[LLVMdev] include/Config/config.h discrepancies between CMake and autofoo builds

Óscar Fuentes ofv at wanadoo.es
Wed Jan 5 13:17:59 PST 2011


Ruben Van Boxem <vanboxem.ruben at gmail.com> writes:

> Well, that's the strong point in the Windows API, backwards
> compatibility is almost infinite! Unix, well, that seems to be a
> completely different story :s...

Don't confuse the Windows API with the C standard library. As mentioned
before, there are no tests for Windows API stuff on the LLVM cmake
build.

> I may be naive, but shouldn't a *standard* C library implementation
> use *standard* headers/function prototypes?

Yes, they should :-)

> I understand OSes like BSD
> and Solaris really suck on this point (standards compliance), but I
> would think linux, Mac OS and Windows at least adhere to a large
> denominator which would make these checks kind of superfluous.

Precisely, VC++ "standard" C library is full of surprises. They add some
with every release.

[snip]



More information about the llvm-dev mailing list