-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 José Fonseca wrote: > On Fri, 2009-09-04 at 13:01 -0700, Ian Romanick wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Brian Paul wrote: >> >>> I'll fix these. >>> >>> Perhaps we should prefix or suffix all the lexer tokens with "T_" or >>> something like that to avoid collisions. Ian? >> Could we just fix it to not include broken Windows header files? > > I doubt. Windows headers have use beyond polluting the global namespace.
Is Mesa using this definition of POINT or SIZE in someway that I'm not aware of? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqi0loACgkQX1gOwKyEAw/D+wCgmLfGhZDvhI5YgTlAfrVPXqBg J3AAnjsDuhPVFMnZzEyfzC0xSvuCeQ1t =zxXe -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
