Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 216.109.114.158 as permitted sender) client-ip=216.109.114.158;
Subject: Re: [lojban] MEX ROI, MEX MOI, MEX MAI
References: <51F15A4D.3030805@lojban.org> <CA+gZtgLWYs4xTNqtBwctM6aMJOpwBLrmYZ65u-eKPAqNFO4V2Q@mail.gmail.com>
From: "John E. Clifford" <kali9putra@yahoo.com>
In-Reply-To: <CA+gZtgLWYs4xTNqtBwctM6aMJOpwBLrmYZ65u-eKPAqNFO4V2Q@mail.gmail.com>
Message-Id: <2BECF054-02C9-41D4-B338-B7944C223103@yahoo.com>
Date: Thu, 25 Jul 2013 17:42:38 -0500
To: "lojban@googlegroups.com" <lojban@googlegroups.com>
Mime-Version: 1.0 (1.0)
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: multipart/alternative;
	boundary=Apple-Mail-AFEB4D39-3F8B-42C9-A86F-44DA7CC5FA99
Content-Transfer-Encoding: 7bit
X-Spam_score: 1.1
X-Spam_score_int: 11
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:  But note that the PEG is working just in case it gives the
    same results as the YACC, the official grammar. Now, later, we may want to
    add some things which that old grammar doesn't allow (but not delete anything
    it does allow) and then this proposal, should it come up and be accepted,
    might find PEG easier to modify. Meanwhile, the incompatibility with YACC
    stops it dead. (Well, barring a long political process of getting the PEG
    declared official and opening the proposed changes process.) [...] 
 
 Content analysis details:   (1.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
                             (kali9putra[at]yahoo.com)
  0.0 DKIM_ADSP_CUSTOM_MED   No valid author signature, adsp_override is
                             CUSTOM_MED
 -0.0 SPF_PASS               SPF: sender matches SPF record
  1.0 FORGED_YAHOO_RCVD      'From' yahoo.com does not match 'Received' headers
  0.0 HTML_MESSAGE           BODY: HTML included in message
  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

--Apple-Mail-AFEB4D39-3F8B-42C9-A86F-44DA7CC5FA99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=ISO-8859-1

But note that the PEG is working just in case it gives the same results as =
the YACC, the official grammar.  Now, later, we may want to add some things=
 which that old grammar doesn't allow (but not delete anything it does allo=
w) and then this proposal, should it come up and be accepted,  might find P=
EG easier to modify.  Meanwhile, the incompatibility with YACC stops it dea=
d.  (Well, barring a long political process of getting the PEG declared off=
icial and opening the proposed changes process.)

Sent from my iPad

On Jul 25, 2013, at 15:37, Ian Johnson <blindbravado@gmail.com> wrote:

> On Thu, Jul 25, 2013 at 1:03 PM, Bob LeChevalier, President and Founder -=
 LLG <lojbab@lojban.org> wrote:
> MOI on the other hand is already tied to MEX at the full grammar level.  =
So I am not sure what it means to say that you cannot use MEX with MOI.  Al=
most anything can be used with MOI if you first turn it into a sumti, and t=
hen apply a ME conversion to that sumti.  You can of course turn a MEX into=
 a sumti using LI, so "meli MEX" with appropriate terminators should work w=
ith MOI.  I just tried it, and you need either a lo'o or a me'u to terminat=
e the li/me construct before the moi.
> I consider ME LI MEX MOI to be a hack, not a proper solution. (Not that i=
t was a bad idea when the goal was to get a YACC working, but it's a bad id=
ea now, when the goal is to get a PEG working.) Simply MEX MOI *should* be =
fine.
>=20
> mi'e la latro'a mu'o
>=20
> --=20
> 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.
> =20
> =20

--=20
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 e=
mail 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.


--Apple-Mail-AFEB4D39-3F8B-42C9-A86F-44DA7CC5FA99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=ISO-8859-1

<html><head></head><body bgcolor=3D"#FFFFFF"><div>But note that the PEG is =
working just in case it gives the same results as the YACC, the official gr=
ammar. &nbsp;Now, later, we may want to add some things which that old gram=
mar doesn't allow (but not delete anything it does allow) and then this pro=
posal, should it come up and be accepted, &nbsp;might find PEG easier to mo=
dify. &nbsp;Meanwhile, the incompatibility with YACC stops it dead. &nbsp;(=
Well, barring a long political process of getting the PEG declared official=
 and opening the proposed changes process.)<br><br>Sent from my iPad</div><=
div><br>On Jul 25, 2013, at 15:37, Ian Johnson &lt;<a href=3D"mailto:blindb=
ravado@gmail.com">blindbravado@gmail.com</a>&gt; wrote:<br><br></div><div><=
/div><blockquote type=3D"cite"><div><div dir=3D"ltr">On Thu, Jul 25, 2013 a=
t 1:03 PM, Bob LeChevalier, President and Founder - LLG <span dir=3D"ltr">&=
lt;<a href=3D"mailto:lojbab@lojban.org" target=3D"_blank">lojbab@lojban.org=
</a>&gt;</span> wrote:<br><div class=3D"gmail_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">MOI on the other =
hand is already tied to MEX at the full grammar level. &nbsp;So I am not su=
re what it means to say that you cannot use MEX with MOI. &nbsp;Almost anyt=
hing can be used with MOI if you first turn it into a sumti, and then apply=
 a ME conversion to that sumti. &nbsp;You can of course turn a MEX into a s=
umti using LI, so "meli MEX" with appropriate terminators should work with =
MOI. &nbsp;I just tried it, and you need either a lo'o or a me'u to termina=
te the li/me construct before the moi.</blockquote>
<div>I consider ME LI MEX MOI to be a hack, not a proper solution. (Not tha=
t it was a bad idea when the goal was to get a YACC working, but it's a bad=
 idea now, when the goal is to get a PEG working.) Simply MEX MOI *should* =
be fine.</div>
<div><br></div><div>mi'e la latro'a mu'o</div></div><br></div></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups "=
lojban" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban+unsubscribe@googlegroups.com">lojban+unsub=
scribe@googlegroups.com</a>.<br>
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com">lojban@googlegroups.com</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/group/lojban">http:=
//groups.google.com/group/lojban</a>.<br>
For more options, visit <a href=3D"https://groups.google.com/groups/opt_out=
">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</div></blockquote></body></html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to lojban+unsubscribe@googlegroups.com.<br />
To post to this group, send email to lojban@googlegroups.com.<br />
Visit this group at <a href=3D"http://groups.google.com/group/lojban">http:=
//groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/groups/opt_out=
">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />

--Apple-Mail-AFEB4D39-3F8B-42C9-A86F-44DA7CC5FA99--