Date: Wed, 19 Feb 2003 22:13:40 -0500 From: Mike Barcroft <mike@FreeBSD.org> To: Tim Robbins <tjr@FreeBSD.ORG> Cc: Craig Rodrigues <rodrigc@attbi.com>, freebsd-standards@FreeBSD.ORG, kan@FreeBSD.ORG Subject: Re: WCHAR_MIN and WCHAR_MAX not defined in <wchar.h> Message-ID: <20030219221340.I61431@espresso.bsdmike.org> In-Reply-To: <20030220141410.A42150@dilbert.robbins.dropbear.id.au>; from tjr@FreeBSD.ORG on Thu, Feb 20, 2003 at 02:14:10PM %2B1100 References: <20030219223313.GA93707@attbi.com> <20030220112847.A36977@dilbert.robbins.dropbear.id.au> <20030219205726.G61431@espresso.bsdmike.org> <20030220141410.A42150@dilbert.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Robbins <tjr@FreeBSD.ORG> writes: > On Wed, Feb 19, 2003 at 08:57:26PM -0500, Mike Barcroft wrote: > > > Tim Robbins <tjr@FreeBSD.org> writes: > > > I'll add a definition of WCHAR_MIN and WCHAR_MAX to <wchar.h> as soon as I > > > can find a clean (non-polluting) way of doing it. > > > > Do we need a <machine/_limits.h> with underscored macro variants? Why > > the specification's authors couldn't keep all the limits in a single > > header, I'll never know. > > That would work. If the real information about limits was in > machine/_limits.h, machine/limits.h would be MI and could be > renamed to sys/limits.h if backwards compatibility was not > an issue. <machine/limits.h> is an implementation detail for userland. We could always make <machine/limits.h> include <sys/limits.h> with an appropriate #warning to transition consumers over. I vote for this option. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030219221340.I61431>