John Polstra wrote:
>
> In article <[EMAIL PROTECTED]>,
> Paul Richards <[EMAIL PROTECTED]> wrote:
> > >
> > > They must not go into <limits.h>. That header file is defined by
> > > the ANSI/ISO C standard. The standard doesn't permit polluting the
> > > namespace with extra stuff.
> >
> > Umm, ok. I don't think our limits.h actually has anything in it that
> > meets the ANSI/ISO standard, every line is ifdef'd :-) Where would be a
> > better place for constants like this?
>
> Sheesh, criticism isn't enough? Now it has to be constructive too? ;-)
>
> I guess it could go into <machine/limits.h> in the
> "!defined(_ANSI_SOURCE)" section. Bruce might have a better idea.
I don't think <machine/limits.h> is the right place. These are constants
that are definately not architecture dependent. The whole problem at the
moment is that the code is abusing architecture dependent constants in
lieu of anything better.
Paul.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
