Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id IAA06672 for ; Sat, 25 Nov 1995 08:51:29 -0500 Message-Id: <199511251351.IAA06672@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id 442A8014 ; Sat, 25 Nov 1995 9:38:41 -0400 Date: Sat, 25 Nov 1995 08:37:31 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: lu'u X-To: lojban@cuvmb.cc.columbia.edu To: John Cowan Status: OR X-From-Space-Date: Sat Nov 25 08:51:31 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU And: >But surely one gardenpaths on that. That is, you'd parse it as > > by e [lua dy] e gy > >until you hit {luu}, and then I guess you'd have to backtrack. Or is >there some quirk of the grammar of LUhU that says it's not elidable >before a sumti connective, so that if you want [lua dy] then you'd have >to say: > > by e lua dy luu e gy > >? And the terminators are not elidable in > > by e lua lae dy luu e gy luu ne zy The nature of LR1 in Lojban is such that given a choice between short and long scope, we must always choose long scope because there is no way in afterthought to extend scope. Thus the moment you see the ".e" you know that the lu'a has not terminated. As a result, i think you correct that the lu'us are required in order to get the parse you want. lojbab