Return-Path: cowan@ccil.org Received: from locke.ccil.org (locke.ccil.org [205.164.136.88]) by xiron.pc.helsinki.fi (8.7.1/8.7.1) with SMTP id VAA06488 for ; Wed, 14 Feb 1996 21:19:10 +0200 Received: from skunk.bpm.ito.chembank.com (cowanj@ritz.mordor.com [165.254.109.51]) by locke.ccil.org (8.6.9/8.6.10) with SMTP id OAA01824 for ; Wed, 14 Feb 1996 14:52:11 -0500 Message-ID: <31223588.1DE8@ccil.org> Date: Wed, 14 Feb 1996 14:18:32 -0500 From: John Cowan Organization: Lojban Central X-Mailer: Mozilla 2.0 (Win16; I) MIME-Version: 1.0 To: veion@XIRON.PC.HELSINKI.FI Subject: Re: GEN: almost-PROPOSAL: intervals References: <199602121648.LAA01061@locke.ccil.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 973 Lines: 19 la veion. cusku di'e > ERROR: the YACC modification I previously sent works at the YACC > level but isn't feasible in practice as the modification > ended up on the lexer side - I'm not yet sure whether it > can be done on the parser side, probably not without a > major modification. Regrettably, it can't. Whatever is done in the preparser rules (900-end) can't refer to things in the earlier rules, on pain of implementing the entire parser within the preparser. So "NOI sentence" within a tense is impossible, even though it YACCs, it doesn't fit the schema of the parser, which is to keep the compounded forms simple. Of these, tense (lexer_O) is already the worst offender, and further complications are truly intolerable. I am still thinking about the other possibilities. I weakly favor messing with "ve'i ", although I recognize the annoying doubled semantics of the i/a/u vowel plus what the sumti actually says.