Hello Kevin and all
I was wondering if anyone had any objections to using JLex to parse our
iCalendar streams. Writing that parser by hand is a tough job, and time is
ticking on.
I have been reluctant to use JLex, but think in the end it can generate a
better parser in less time. Writing the parser by hand is just too labor
intensive.
Pros
1. After the initial learning curve this could save significant
development time.
2. When you want to drive a nail into wood use a hammer, JLex is
specifically designed to do parsing.
3. Supporting another open source project.
Cons
1. For those not familiar with lexical analyzers. They use .lex files to
generate source code files. In the case of Jlex a Jlex .lex file generates
java code. Anyway, some people dont like autogeneration of source.
Comments....
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
