From owner-freebsd-hackers Tue Sep 19 22:18:06 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA17865 for hackers-outgoing; Tue, 19 Sep 1995 22:18:06 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA17860 for ; Tue, 19 Sep 1995 22:18:04 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id WAA15752; Tue, 19 Sep 1995 22:10:56 -0700 From: Terry Lambert Message-Id: <199509200510.WAA15752@phaeton.artisoft.com> Subject: Re: Policy on printf format specifiers? To: bde@zeta.org.au (Bruce Evans) Date: Tue, 19 Sep 1995 22:10:56 -0700 (MST) Cc: bakul@netcom.com, terry@lambert.org, freebsd-hackers@freefall.freebsd.org, hsu@cs.hut.fi In-Reply-To: <199509200455.OAA10868@godzilla.zeta.org.au> from "Bruce Evans" at Sep 20, 95 02:55:30 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 826 Sender: owner-hackers@FreeBSD.org Precedence: bulk > >I don't really care whether I have to add additional unsigned short based > >functions or not, though using wchar_t as a 16 bit unsigned value would > >save a lot of code duplication and kernel bloat. > > You have to add additional u_int16_t based functions to support externally > imposed 16-bit storage formats, and u_int32_t based functions to support > 32-bit storage formats (not to mention u_int36_t based functions to > support 36-bit storage formats :-). I don't know of *any* file system that uses 4 byte characters to store directory entries. I know of two that use 16. 36 bit: I don't have a DEC KL10 or Harris system. Are you saying there is a port in progess? 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.