[ofa-general] Re: [PATCH] management: uint -> unsigned replacement

[Jason Gunthorpe]

On Tue, Jun 26, 2007 at 03:18:55PM -0400, Hal Rosenstock wrote:

> > > > > compatibility name for C type".  This type might not defined e.g. if
> > > > > __STRICT_ANSI__ is set,
> > > > 
> > > > Is strict ANSI a requirement ?
> > 
> > Even if not,
> 
> I was just trying to determine how much further we needed to go down
> this path.

As a general rule if you can compile each of your public headers files
with:

echo '#include "foo.h"' > t.c
gcc -Wall -ansi t.c

You are doing OK. What is in your private .c files isn't that
important (and I'd advocate using -std=gnu99, but I never compile with
VC++ :P).

'gcc -ansi -D_POSIX_SOURCE_' as a minimum is also pretty good.

Jason