From owner-freebsd-standards Wed Feb 19 19:14:40 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F8F737B401; Wed, 19 Feb 2003 19:14:39 -0800 (PST) Received: from dilbert.robbins.dropbear.id.au (184.b.005.mel.iprimus.net.au [210.50.41.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EBE143F75; Wed, 19 Feb 2003 19:14:37 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au (mzz61kjiusi6be1s@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6) with ESMTP id h1K3ETFa042422; Thu, 20 Feb 2003 14:14:30 +1100 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6/Submit) id h1K3EApB042421; Thu, 20 Feb 2003 14:14:10 +1100 (EST) (envelope-from tim) Date: Thu, 20 Feb 2003 14:14:10 +1100 From: Tim Robbins To: Mike Barcroft Cc: Craig Rodrigues , freebsd-standards@FreeBSD.ORG, kan@FreeBSD.ORG Subject: Re: WCHAR_MIN and WCHAR_MAX not defined in Message-ID: <20030220141410.A42150@dilbert.robbins.dropbear.id.au> References: <20030219223313.GA93707@attbi.com> <20030220112847.A36977@dilbert.robbins.dropbear.id.au> <20030219205726.G61431@espresso.bsdmike.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030219205726.G61431@espresso.bsdmike.org>; from mike@FreeBSD.ORG on Wed, Feb 19, 2003 at 08:57:26PM -0500 Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 19, 2003 at 08:57:26PM -0500, Mike Barcroft wrote: > Tim Robbins writes: > > I'll add a definition of WCHAR_MIN and WCHAR_MAX to as soon as I > > can find a clean (non-polluting) way of doing it. > > Do we need a 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. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message