Hi Giannis, --- Giannis Georgalis <[EMAIL PROTECTED]> wrote: > Stephen Crawley <[EMAIL PROTECTED]> writes: > > > I'd recommend hand building a pure Java parser. > That way, the Classpath > > build process doesn't depend on an external parser > or lexer generator, > > and the source code will be easier to understand. > > We could include the generated files (as Brian also > noted) and avoid > the exotic dependencies. However, I was dissapointed > to find out, > that jlex and jflex did not support parsing from a > string (flex > supports it). That changed radically my plans... and > on a second > thought native code with flex goes too much.
No need to get radical. ;) As long as the parser generator of your choice accepts input form some kind of InputStream or Reader, you could wrap the String in the appropriate java.io class and use that. > > Finally, the chance that the RFC URI syntax will > change radically is pretty > > small, IMO. > > You are probably right ... but don't forget M$, > they'll want to make > their very own extensions to URI, sun will have to > follow them > etc. ;-) that's purely hypothetical. There is already a simple mechanism for domain specific URIs and it's called a scheme. cheers, dalibor topic __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
