From lojban-out@lojban.org Thu Nov 08 12:27:05 2007 Return-Path: X-Sender: lojban-out@lojban.org X-Apparently-To: lojban@yahoogroups.com X-Received: (qmail 65797 invoked from network); 8 Nov 2007 20:27:05 -0000 X-Received: from unknown (66.218.67.96) by m36.grp.scd.yahoo.com with QMQP; 8 Nov 2007 20:27:05 -0000 X-Received: from unknown (HELO mail2.sea5.speakeasy.net) (69.17.117.4) by mta17.grp.scd.yahoo.com with SMTP; 8 Nov 2007 20:27:05 -0000 X-Received: (qmail 30524 invoked from network); 8 Nov 2007 20:27:03 -0000 X-Received: from chain.digitalkingdom.org ([64.81.66.169]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 8 Nov 2007 20:27:03 -0000 X-Received: from lojban-out by chain.digitalkingdom.org with local (Exim 4.67) (envelope-from ) id 1IqDxs-0001G3-8Q for lojban@yahoogroups.com; Thu, 08 Nov 2007 12:27:01 -0800 X-Received: from chain.digitalkingdom.org ([64.81.66.169]) by chain.digitalkingdom.org with esmtp (Exim 4.67) (envelope-from ) id 1IqDxQ-00018t-SB; Thu, 08 Nov 2007 12:26:35 -0800 X-Received: with ECARTIS (v1.0.0; list lojban-list); Thu, 08 Nov 2007 12:24:57 -0800 (PST) X-Received: from nobody by chain.digitalkingdom.org with local (Exim 4.67) (envelope-from ) id 1IqDvr-00018a-83 for lojban-list-real@lojban.org; Thu, 08 Nov 2007 12:24:56 -0800 X-Received: from wr-out-0506.google.com ([64.233.184.226]) by chain.digitalkingdom.org with esmtp (Exim 4.67) (envelope-from ) id 1IqDvj-00017y-AS for lojban-list@lojban.org; Thu, 08 Nov 2007 12:24:55 -0800 X-Received: by wr-out-0506.google.com with SMTP id 36so164570wra for ; Thu, 08 Nov 2007 12:24:45 -0800 (PST) X-Received: by 10.86.58.3 with SMTP id g3mr824688fga.1194553484042; Thu, 08 Nov 2007 12:24:44 -0800 (PST) X-Received: by 10.86.86.13 with HTTP; Thu, 8 Nov 2007 12:24:44 -0800 (PST) Message-ID: <925d17560711081224i177601ecmb2e485f4adb687f0@mail.gmail.com> Date: Thu, 8 Nov 2007 17:24:44 -0300 In-Reply-To: <737b61f30711080933s23ebe987ib8970e3dcbe6fc33@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <737b61f30711080933s23ebe987ib8970e3dcbe6fc33@mail.gmail.com> X-Spam-Score: 0.0 X-Spam-Score-Int: 0 X-Spam-Bar: / X-archive-position: 13910 X-ecartis-version: Ecartis v1.0.0 Errors-to: lojban-list-bounce@lojban.org X-original-sender: jjllambias@gmail.com X-list: lojban-list X-Spam-Score: 0.0 X-Spam-Score-Int: 0 X-Spam-Bar: / To: lojban@yahoogroups.com X-Originating-IP: 69.17.117.4 X-eGroups-Msg-Info: 1:12:0:0:0 X-eGroups-From: "=?ISO-8859-1?Q?Jorge_Llamb=EDas?=" From: "=?ISO-8859-1?Q?Jorge_Llamb=EDas?=" Reply-To: jjllambias@gmail.com Subject: [lojban] Re: peg grammar parse tree cmavo X-Yahoo-Group-Post: member; u=116389790; y=nzJtEnR600NEVZf3QISgBzkDzBtHIlpx3uQuaUOa3b9cBL2AGA X-Yahoo-Profile: lojban_out X-Yahoo-Message-Num: 28388 On 11/8/07, Chris Capel wrote: > > From a layout standpoint, I think it would make more sense to have it > in the morphology. I agree, it does make sense. > But either might have a performance penalty. This might actually improve performance, because checking whether it is a cmavo in general has to be more costly than checking whether it is a particular cmavo. > "A-pre <- pre-clause A:cmavo spaces?" > > "cmavo" there would just be a label that affects the parse tree, > creating an extra node called "cmavo" that contains "A". > > What do you think? Could you instead have: "A:cmavo <- &cmavo ( a / e / j i / o / u ) &post-word" That would seem cleaner than having the label in the A-pre rule. mu'o mi'e xorxes To unsubscribe from this list, send mail to lojban-list-request@lojban.org with the subject unsubscribe, or go to http://www.lojban.org/lsg2/, or if you're really stuck, send mail to secretary@lojban.org for help.