Date: Mon, 13 Mar 2000 01:57:17 +0000 From: Paul Richards <paul@originative.co.uk> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: MAX_UID ? Message-ID: <38CC4AFD.7E649664@originative.co.uk> References: <38CAD957.3C839375@originative.co.uk> <200003120430.UAA49807@vashon.polstra.com> <38CB322D.D12ED0B0@originative.co.uk> <200003130145.RAA51429@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra wrote: > > In article <38CB322D.D12ED0B0@originative.co.uk>, > Paul Richards <paul@originative.co.uk> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38CC4AFD.7E649664>