From lojban@cuvmb.bitnet Wed Mar 13 23:33:33 1996 Received: from punt4.demon.co.uk by stryx.demon.co.uk with SMTP id AA10829 ; Wed, 13 Mar 96 23:33:31 GMT Received: from punt-4.mail.demon.net by mailstore for ia@stryx.demon.co.uk id 826737539:10329:1; Wed, 13 Mar 96 17:18:59 GMT Received: from cunyvm.cuny.edu ([128.228.1.2]) by punt-4.mail.demon.net id aa09783; 13 Mar 96 17:17 GMT Received: from CUVMB.CC.COLUMBIA.EDU by CUNYVM.CUNY.EDU (IBM VM SMTP V2R3) with BSMTP id 7034; Wed, 13 Mar 96 12:17:42 EST Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 5480; Wed, 13 Mar 96 12:18:08 EDT Date: Wed, 13 Mar 1996 14:26:10 -0300 Reply-To: "Jorge J. Llambias" Sender: Lojban list From: "Jorge J. Llambias" Subject: Re: TECH: PROPOSED GRAMMAR CHANGE 2$i To: lojban@cuvmb.cc.columbia.edu Message-ID: <826737479.9783.0@cunyvm.cuny.edu> Status: R la veion mi di'e spuda >> Couldn't it be just "GEK terms /NUhU/ GIK >> terms /NUhU/"? That would make it much more in tune with the >> general use of geks. > > This would work at the yacc level > >> (Even better if the first NUhU could be avoided.) > > 1 shift/reduce conflict Is it possible to identify when this happens? When a {gi} is found, the only possibility is that it is closing the latest open gek, isn't it? In other words, under what circumstances would the first nu'u not be elidable? Jorge