From owner-freebsd-hackers Mon May 14 17:45: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 08B8B37B423 for ; Mon, 14 May 2001 17:45:05 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f4F0j3F05269; Mon, 14 May 2001 17:45:03 -0700 (PDT) Date: Mon, 14 May 2001 17:45:02 -0700 From: Alfred Perlstein To: Erik Trulsson Cc: hackers@FreeBSD.ORG Subject: Re: wint_t Message-ID: <20010514174502.J2009@fw.wintelcom.net> References: <20010514164401.A61243@dragon.nuxi.com> <20010515023221.A41666@student.uu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010515023221.A41666@student.uu.se>; from ertr1013@student.uu.se on Tue, May 15, 2001 at 02:32:22AM +0200 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Erik Trulsson [010514 17:32] wrote: > On Mon, May 14, 2001 at 04:44:01PM -0700, David O'Brien wrote: > > What is the proper definition of wint_t? curses.h has it as a "long int", > > however NetBSD (and GCC's libstdc++) has it as an "int". > > > > I think either definition is fine. It should be at least as wide as a > wchar_t. stddef.h has wchar_t as "int" while curses.h defines wchar_t > (if it isn't defined in stddef.h) as "unsigned long". > > The C standard says that wchar_t should be able to all members of thye > largest extended chracter set. AFAIK FreeBSD doesn't have any character > set which requires more than 8 bits. > wint_t should also be able to hold all members of the largest character > set plus one extra value (WEOF). Also it must be at least 16 bits. Wouldn't it be kinda painful unless we did this with a 16 bit type? -- -Alfred Perlstein - [alfred@freebsd.org] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message