Date: Thu, 20 Feb 2003 21:45:25 -0500 From: Craig Rodrigues <rodrigc@attbi.com> To: freebsd-standards@freebsd.org Cc: kan@freebsd.org Subject: Re: WCHAR_MIN and WCHAR_MAX not defined in <wchar.h> Message-ID: <20030221024525.GA35437@attbi.com> In-Reply-To: <20030219221340.I61431@espresso.bsdmike.org> References: <20030219223313.GA93707@attbi.com> <20030220112847.A36977@dilbert.robbins.dropbear.id.au> <20030219205726.G61431@espresso.bsdmike.org> <20030220141410.A42150@dilbert.robbins.dropbear.id.au> <20030219221340.I61431@espresso.bsdmike.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 19, 2003 at 10:13:40PM -0500, Mike Barcroft wrote: > <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. Sounds good to me. The reason why I am interested in this stuff is to get wchar_t support working in GCC on FreeBSD. Alex Kabaev listed the problems in FreeBSD which prevent the GCC configure process from properly using wchar_t in libstdc++: http://gcc.gnu.org/ml/gcc/2003-02/msg01291.html The lack of WCHAR_MIN/WCHAR_MAX in <wchar.h> was one of the problems. Do you need any help implementing <machine/_limits.h>? -- Craig Rodrigues http://home.attbi.com/~rodrigc rodrigc@attbi.com 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?20030221024525.GA35437>