-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Paul wrote: > Ian Romanick wrote: > >> It will probably a bit before I can add support to the parser. I'm >> still trying to understand how src/mesa/shader/grammar works (and why >> that was used instead of flex & byacc). > > The ARB program parser is a bit of a mystery to me too. > > If I'd rewrite the parsers toay I'd probably use lex/yacc. I originally > implemented my own recursive descent parsers for the NV extensions > because the language was pretty simple. Judging from LOC and > understandability, I don't think I did too bad.
How would using lex & yacc impact non-Unix builds? Meaning, will that cause problems on Windows and Mac OS? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDb792X1gOwKyEAw8RAoYiAJ93YlQyIcvcdeFbuyofLDDJINzh2QCeNN7O 51FrMDbRFQ0uEocRULN5BGg= =dc3e -----END PGP SIGNATURE----- ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
