From nobody@digitalkingdom.org Sun Dec 28 01:37:50 2008 Received: with ECARTIS (v1.0.0; list lojban-list); Sun, 28 Dec 2008 01:37:51 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.69) (envelope-from ) id 1LGs5m-000813-9E for lojban-list-real@lojban.org; Sun, 28 Dec 2008 01:37:50 -0800 Received: from rlpowell by chain.digitalkingdom.org with local (Exim 4.69) (envelope-from ) id 1LGs5m-00080w-7i for lojban-list@lojban.org; Sun, 28 Dec 2008 01:37:50 -0800 Date: Sun, 28 Dec 2008 01:37:50 -0800 From: Robin Lee Powell To: lojban-list@lojban.org Subject: [lojban] Re: gleki xisri'i Message-ID: <20081228093750.GW10930@digitalkingdom.org> Mail-Followup-To: lojban-list@lojban.org References: <20081228012723.GA3821@sdf.lonestar.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081228012723.GA3821@sdf.lonestar.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-archive-position: 15176 X-ecartis-version: Ecartis v1.0.0 Sender: lojban-list-bounce@lojban.org Errors-to: lojban-list-bounce@lojban.org X-original-sender: rlpowell@digitalkingdom.org Precedence: bulk Reply-to: lojban-list@lojban.org X-list: lojban-list On Sun, Dec 28, 2008 at 01:27:25AM +0000, Minimiscience wrote: > mulno .ui .o'u > > I've fixed my patch for the grammar; the problem was simply that > discursive {bridi} (and presumably other free modifiers) weren't > binding as tightly as they should have. The output from the > patched parser now matches that of the original parser, and the > final patch can be found at > . > Hopefully, the grammar now works exactly as it's supposed to. I haven't tested it thoroughly (I actually have a big script set for this purpose), but so far it seems to be doing pretty well. > As to the question of what the difference between using `error' > and using `%prec' is, I'm not entirely sure what you want me to > say. `%prec' uses features as they were intended and is better > (and less obfuscated) style? Specifying how to resolve > shift/reduce conflicts is more understandable & portable than > error recovery? Using `error' here is like passing void pointers > to structures that start with a type-identifying integer in an > effort to implement polymorphism when you could just code in C++? > It "just works"? Both ways get the job done, but using %prec is > the way that it's supposed to get done. .u'u sai I'm so sorry; I phrased that poorly and I've been rude to you. Yes, this solution is *substantially* better than the extant trick that the official parser uses. I'm particularily curious to see what code can be removed with this version (i.e. the error handling code). For the record, looking at the changelog seems to indicate that %prec may not actually have existed when the official parser was made. I'm just disappointed that this doesn't seem to put us any closer to an actual CFG for Lojban (not that I've analyzed it properly; been busy). I was way too excited when I saw your first post. Sorry if I was an ass. -Robin -- They say: "The first AIs will be built by the military as weapons." And I'm thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ 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.