From owner-freebsd-hackers Thu Sep 21 11:08:27 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23290 for hackers-outgoing; Thu, 21 Sep 1995 11:08:27 -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 LAA23283 for ; Thu, 21 Sep 1995 11:08:17 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA09066; Thu, 21 Sep 1995 11:06:55 -0700 From: Terry Lambert Message-Id: <199509211806.LAA09066@phaeton.artisoft.com> Subject: Re: Policy on printf format specifiers? To: peter@taronga.com (Peter da Silva) Date: Thu, 21 Sep 1995 11:06:55 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199509210338.WAA13478@bonkers.taronga.com> from "Peter da Silva" at Sep 20, 95 10:38:36 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: 900 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > >> What information loss is that? > > >How many records are in the file from stat information. > > And how is this information *lost*? Your code works just fine regardless > of the character set used. I replied to this under seperate cover, but since you hit the list, I'll hit the list too: Records must do one of three things with Runic encoding schemes: 1) Not contain a fixed amount of data for a fixed length field. 2) Be larger than they have to be to take runic expansion into account for fixed length fields, with a high average wastage. 3) Be variable length, giving up the relationship between file size and record count. 1 and 2 are unacceptable. 3 is unacceptable. Runic encoding is unacceptable (and this is just one reason among many). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.