On Mon, 11 Feb 2008, H.Merijn Brand wrote: > Having to answer questions about my C-compiler isn't always that easy. > Sometimes you need to find include files, for which you don't know if > and if how they are used. Sometimes you need to compile test programs > to see the behaviour, and then there is threads, 32/64 bitness etc. > > I was recently pointed to http://www.math.utah.edu/pub/features/ > Which gives a nice summary of what your C/C++ compiler behaves like. > Here's the output for HP C-ANSI-C on HP-UX 11.23/64 IPF and on 11.00 Hmm. I'm actually more curious about what language features a compiler supports (Is "inline" a keyword? Does it accept C99 comments? C99 struct initializers? Flex arrays?). Sometimes the errors you get when these aren't what the code expects are hard to identify, because the compiler comes up with some odd interpretation of the structure as what you meant but messed up, and you get a slew of inappropriate error messages, sometimes hiding the actual wrong thing. Missing header files/types/macros/declarations generally give a clear first error message. -Daniel *This .sig left intentionally blank* - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
