Re: future-proof parsing

I write all my new parsers and scanners using ml-antlr and ml-ulex.
While ml-yacc will continue to be supported, I expect that ml-ulex will
eventually completely replace ml-lex, since the compatibility mode
allows ml-ulex to be used in place of ml-lex (and the ml-lex code base
is horrible).

If there are aspects of the ml-lpt docs that you think need improvement,
please file a feature request at https://smlnj-gforge.cs.uchicago.edu/bugform.php

	- John


On Dec 18, 2009, at 4:53 AM, Gergely Buday wrote:

> Dear SML/NJ developers,
> 
> there does not seem too much activity around ml-ulex and ml-antlr, at
> least from the documentation viewpoint - it is almost three years old
> and fragmented. If I started a new parser today, would you recommend
> me to switch back to ml-lex and ml-yacc, being more tested and mature?
> My input is strictly ASCII.
> 
> - Gergely
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________
> Smlnj-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/smlnj-list
> 


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev