From lojban@cuvmb.bitnet Wed Mar 13 23:33:43 1996 Received: from punt4.demon.co.uk by stryx.demon.co.uk with SMTP id AA10831 ; Wed, 13 Mar 96 23:33:40 GMT Received: from punt-4.mail.demon.net by mailstore for ia@stryx.demon.co.uk id 826750394:02752:1; Wed, 13 Mar 96 20:53:14 GMT Received: from cunyvm.cuny.edu ([128.228.1.2]) by punt-4.mail.demon.net id aa02423; 13 Mar 96 20:52 GMT Received: from CUVMB.CC.COLUMBIA.EDU by CUNYVM.CUNY.EDU (IBM VM SMTP V2R3) with BSMTP id 8104; Wed, 13 Mar 96 15:51:48 EST Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 6937; Wed, 13 Mar 96 15:52:15 EDT Date: Wed, 13 Mar 1996 22:50:29 +0200 Reply-To: Veijo Vilva Sender: Lojban list From: Veijo Vilva Subject: Re: TECH: PROPOSED GRAMMAR CHANGE 2$i X-To: lojban@cuvmb.cc.columbia.edu To: Multiple recipients of list LOJBAN Message-ID: <826750347.2423.0@cunyvm.cuny.edu> Status: R > Date: Wed, 13 Mar 1996 14:26:10 -0300 > From: "Jorge J. Llambias" > Subject: Re: TECH: PROPOSED GRAMMAR CHANGE 2$i >>> (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? After some juggling I found a solution at the YACC level: --- in the rules for term_set_83 replace GEK_807 terms_80 GIK_816 NUhU_gap_460 terms_80 NUhU_gap_460 with GEK_807 terms_80 term_81 GIK_816 terms_80 term_81 NUhU_gap_460 Now, a termset must have at least two terms. co'o mi'e veion --------------------------------- .i mi du la'o sy. Veijo Vilva sy. ---------------------------------