Received-SPF: pass (google.com: domain of blindbravado@gmail.com designates 2607:f8b0:4003:c01::22d as permitted sender) client-ip=2607:f8b0:4003:c01::22d;
MIME-Version: 1.0
In-Reply-To: <51F15A4D.3030805@lojban.org>
References: <51F15A4D.3030805@lojban.org>
Date: Thu, 25 Jul 2013 16:37:04 -0400
Message-ID: <CA+gZtgLWYs4xTNqtBwctM6aMJOpwBLrmYZ65u-eKPAqNFO4V2Q@mail.gmail.com>
Subject: Re: [lojban] MEX ROI, MEX MOI, MEX MAI
From: Ian Johnson <blindbravado@gmail.com>
To: lojban@googlegroups.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: multipart/alternative; boundary=047d7b414176345a3804e25bfd51
X-Spam_score: -0.1
X-Spam_score_int: 0
X-Spam_bar: /

--047d7b414176345a3804e25bfd51
Content-Type: text/plain; charset=ISO-8859-1

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.
>  Almost anything can be used with MOI if you first turn it into a sumti,
> and then 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 with MOI.  I just tried it, and you need either a lo'o or a me'u to
> terminate the li/me construct before the moi.

I consider ME LI MEX MOI to be a hack, not a proper solution. (Not that 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.

mi'e la latro'a mu'o

-- 
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.


--047d7b414176345a3804e25bfd51
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Jul 25, 2013 at 1:03 PM, Bob LeChevalier, Presiden=
t and Founder - LLG <span dir=3D"ltr">&lt;<a href=3D"mailto:lojbab@lojban.o=
rg" 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. =A0So I am not sure =
what it means to say that you cannot use MEX with MOI. =A0Almost anything c=
an be used with MOI if you first turn it into a sumti, and then apply a ME =
conversion to that sumti. =A0You can of course turn a MEX into a sumti usin=
g LI, so &quot;meli MEX&quot; with appropriate terminators should work with=
 MOI. =A0I just tried it, and you need either a lo&#39;o or a me&#39;u to t=
erminate 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&#39;s a=
 bad idea now, when the goal is to get a PEG working.) Simply MEX MOI *shou=
ld* be fine.</div>
<div><br></div><div>mi&#39;e la latro&#39;a mu&#39;o</div></div><br></div><=
/div>

<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 />

--047d7b414176345a3804e25bfd51--