uint [was: [cvs] base64.h ... ]

[David Relson]

On Sun, 25 Jan 2004 12:03:31 +0100
Matthias Andree wrote:

> On Sat, 24 Jan 2004, David Relson wrote:

...[snip]...

> > "uint" has been fine for the last 18 months, why change now?  What
> > platform(s) have trouble with uint?  I don't like "dumbing down" our
> > code and making it hard to read in order to accommodate an unusual
> > platform.
> 
> uint is a non-standard type, and we didn't include according headers
> to define it before *using* this type, that used to be the problem,
> which showed with various compilers in strict mode.
> 
> OTOH, I am no particular friend of "deep" includes that pull lots of
> other files in, because this affects (adversely) the compilation of
> all files.
> 
> We'd then need our own bftypes.h include that doesn't include anything
> itself but config.h.

We already have system.h for handling type issues.  If we need uint,
that's the place to define it.

There's no need for bftypes.h.