On 2/20/08, Ian Romanick <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Keith Whitwell wrote: > | Ian Romanick wrote: > |> José Fonseca wrote: > |> | Microsoft compilers don't support C99 syntax. The only native windows > |> | compilers that support C99 syntax are mingw32-gcc and Intel C/C++ > |> | compiler, but we can't seriously support windows platform by targeting > |> | these compilers alone and leave msvc out. > |> > |> In a word, NO. Frankly, I don't care to be restricted to 20 year old C > |> syntax just because Microsoft doesn't care to support the 10 year old C > |> syntax. > | > | Well, in the core parts of gallium this will hold. For the Cell driver > | it doesn't matter so much... > | > | It's hardly ideal but we're basically grownups here and can probably > | take it in our stride, especially given that the same restrictions have > | been historically enforced in core Mesa. > > But this has not been the case in the hardware driver code. Isn't this > code being folded into gallium (i.e., i965simple)? In that code we > routinely use variadic macros, C99 array initializers, and C99 structure > initializers...and it makes the code better.
It actually was when I tried to compile this code with msvc and saw all the compile errors and all the necessary effort to fix it that I decided to write this thread. Basically, using -stc=c99 with gallium code hides this problem until it is quite big. Jose ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
