[Devel] Re: [Freetype] Summary of ANSI preprocessor trouble..

[David Turner]

Hi Bob,

> 
> It really does not matter what the real ANSI C standard says.  The
> goal should be to find the most useful common denominator which works
> across all compilers that might be conceivably be used to compile
> FreeType.
> 
Granted, but there are chances that this common denominator is extremely
close to the standard, isn't it ??

> It is unlikely that compilers will be fixed to work with FreeType so
> FreeType must therefore be adjusted to work with all compilers which
> claim to be ANSI C compliant (and produce correct code).
>
Pre-processing is an integral part of the ANSI C standard. A compiler
that claims compliance without the appropriate cpp is simply wrong..

I just want to devote the least resources on supported _broken_
compilers, there are much better things to do.. to me, it seems
ANSI is the only stick we can conveniently cling to..

> I have access to the ANSI C++ standard if we must have a standard to
> look at.
> 
note that there is also the ANSI C Rationale available at:

  http://www.lysator.liu.se/c/rat/title.html 

it is not the standard per se, but describes why certain things
were designed the way they were, and is a very informative document.

Regards,

- David