Received-SPF: pass (google.com: domain of seladwa@gmx.de designates 212.227.17.20 as permitted sender) client-ip=212.227.17.20;
Message-ID: <51F0193D.80006@gmx.de>
Date: Wed, 24 Jul 2013 20:13:17 +0200
From: selpa'i <seladwa@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: lojban@googlegroups.com
Subject: Re: [lojban] MEX ROI, MEX MOI, MEX MAI
References: <CA+gZtgLznD8zjE9tRULYxWXwrF_R__AxuoyWehK2pqgXXSYPMA@mail.gmail.com>
In-Reply-To: <CA+gZtgLznD8zjE9tRULYxWXwrF_R__AxuoyWehK2pqgXXSYPMA@mail.gmail.com>
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Spam_score: 0.1
X-Spam_score_int: 1
X-Spam_bar: /
X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  la latro'a cu cusku di'e > Today we found that you can't use
    MEX with ROI, MOI, or MAI, even in the > PEG. camxes treats a closed MEX
   (e.g. {vei mo'e ko'a [te'u ve'o]} as a > "quantifier", distinct from PA* (i.e.
    PA* = PA | PA PA*), which it calls > a "number". With MOI we have the YACC-friendly
    hack "ME LI MEX MOI", > which still cooperates with the PEG, but as best
   I can tell there is no > such hack for ROI and MAI. > > Would anything go
   wrong if MEX ROI, MEX MOI, and MEX MAI were made > allowed in the PEG? [...]
    
 
 Content analysis details:   (0.1 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: lojban.org]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (seladwa[at]gmx.de)
  0.0 RCVD_IN_DNSWL_BLOCKED  RBL: ADMINISTRATOR NOTICE: The query to DNSWL
                             was blocked.  See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [209.85.216.183 listed in list.dnswl.org]
 -0.0 SPF_PASS               SPF: sender matches SPF record
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
  0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid

la latro'a cu cusku di'e
> Today we found that you can't use MEX with ROI, MOI, or MAI, even in the
> PEG. camxes treats a closed MEX (e.g. {vei mo'e ko'a [te'u ve'o]} as a
> "quantifier", distinct from PA* (i.e. PA* = PA | PA PA*), which it calls
> a "number". With MOI we have the YACC-friendly hack "ME LI MEX MOI",
> which still cooperates with the PEG, but as best I can tell there is no
> such hack for ROI and MAI.
>
> Would anything go wrong if MEX ROI, MEX MOI, and MEX MAI were made
> allowed in the PEG?

It goes beyond LALR(1), but that's about it as far as I can tell. It's 
not a problem in a PEG. See this mekso proposal by xorxes, which I 
strongly support:

http://www.lojban.org/tiki/MEX+grammar+proposal

This would allow any MEX where you can use a quantifier right now. It 
would also remove the need for {vei ... ve'o} brackets, something I 
always found unnatural.

 > If not, can we get this into camxes?

Hehe, I'm not sure camxes can just be changed to incorporate unofficial 
changes. Someone would have to make it official first (*hint*).

mu'o mi'e la selpa'i

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.