Received: from mail-ye0-f185.google.com ([209.85.213.185]:41118) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1V2Owh-0002Qm-H1 for lojban-list-archive@lojban.org; Thu, 25 Jul 2013 10:03:38 -0700 Received: by mail-ye0-f185.google.com with SMTP id l10sf232016yen.12 for ; Thu, 25 Jul 2013 10:03:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-beenthere:x-ct-class:x-ct-score:x-ct-refid:x-ct-spam :x-authority-analysis:x-cm-score:message-id:date:from:organization :user-agent:mime-version:to:subject:references:in-reply-to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; bh=JY1PX/n7buHBoZyHQJuBRvC5VWX3V/BYryNCkG9gVGM=; b=aXwzLgpHi6ccHlSn0RVteVdVAahM4XfKPfNWf94SKRrRxG5x8roR1krUZjEkGXhssB WhgVef/iEHAnEvGzpEMXKsI7pqdaeiu/aDvgMAgwlTAeO9zGQ9vdpIpzC5HJSnzUm8Lo rMvXmLd/fqaTu3+DfPkf9kK2LCN/f4Bo3Kd90f/lxgPwsjjScnugwA+8mw9iX28PTQte IKsFmz5oXj3PFNrPSXEupdGETC+C26dMsXIvBYI3crQlIayoH2yFzDBUAK1bHWYvQhlm 4hkiJeRr9nOSacJcFuHDHG2sgQSdSPUafVpixGv+Us/IDsMuWYECxSI86fIKpim7lnrO 2Blg== X-Received: by 10.49.3.104 with SMTP id b8mr1620157qeb.25.1374771793198; Thu, 25 Jul 2013 10:03:13 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.49.12.233 with SMTP id b9ls688222qec.14.gmail; Thu, 25 Jul 2013 10:03:12 -0700 (PDT) X-Received: by 10.52.176.102 with SMTP id ch6mr903159vdc.3.1374771792793; Thu, 25 Jul 2013 10:03:12 -0700 (PDT) Received: from eastrmfepo103.cox.net (eastrmfepo103.cox.net. [68.230.241.215]) by gmr-mx.google.com with ESMTP id s12si390029qcw.1.2013.07.25.10.03.12 for ; Thu, 25 Jul 2013 10:03:12 -0700 (PDT) Received-SPF: neutral (google.com: 68.230.241.215 is neither permitted nor denied by best guess record for domain of lojbab@lojban.org) client-ip=68.230.241.215; Received: from eastrmimpo305 ([68.230.241.237]) by eastrmfepo103.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130725170312.YBCV3894.eastrmfepo103.cox.net@eastrmimpo305> for ; Thu, 25 Jul 2013 13:03:12 -0400 Received: from [192.168.0.100] ([72.209.248.61]) by eastrmimpo305 with cox id 4h391m00M1LDWBL01h39ME; Thu, 25 Jul 2013 13:03:12 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.51F15A50.0068,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=c8x1t2Bl c=1 sm=1 a=z9jnGXjs1dxvEuWvIXKNSw==:17 a=YsUzL_8ObRgA:10 a=6Jg1OvfoIAcA:10 a=xmHE3fpoGJwA:10 a=8nJEP1OIZ-IA:10 a=8YJikuA2AAAA:8 a=RAhXSfCFj9oA:10 a=JUQa0qIU1yYsQZpZWX8A:9 a=wPNLvfGTeEIA:10 a=dxBpO5_FDU0A:10 a=z9jnGXjs1dxvEuWvIXKNSw==:117 X-CM-Score: 0.00 Message-ID: <51F15A4D.3030805@lojban.org> Date: Thu, 25 Jul 2013 13:03:09 -0400 From: "Bob LeChevalier, President and Founder - LLG" Organization: The Logical Language Group, Inc. User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: lojban@googlegroups.com Subject: Re: [lojban] MEX ROI, MEX MOI, MEX MAI References: <4Hk11m02656Cr6M01Hk2BG> In-Reply-To: <4Hk11m02656Cr6M01Hk2BG> X-Original-Sender: lojbab@lojban.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 68.230.241.215 is neither permitted nor denied by best guess record for domain of lojbab@lojban.org) smtp.mail=lojbab@lojban.org Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / Ian Johnson wrote: > 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? If not, can we get this into camxes? I don't know anything about the PEG grammar (or camxes), but for YACC and the official grammar, there is a fundamental problem. ROI is defined and used solely in the "preparser" that constructs strings of cmavo into tenses. MEX is defined at the full grammar level, and has delimited recursive components that in theory could include pretty much the whole grammar (not that I think anyone uses such functionality). It might be possible to add some rules to expand the set of cmavo strings that the preparser would accept for ROI, but it would have to be done carefully (IIRC, we had a bear of a time getting logical tense compounds to work because of FIHO), and it wouldn't include most of MEX. I believe that MAI is handled in the UI "grammar", and hence is even pre- preparser 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. -- Bob LeChevalier lojbab@lojban.org www.lojban.org President and Founder, The Logical Language Group, Inc. -- 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.