From owner-freebsd-hackers  Tue Sep 19 21:47:29 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA16642
          for hackers-outgoing; Tue, 19 Sep 1995 21:47:29 -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 VAA16630
          for <hackers@freebsd.org>; Tue, 19 Sep 1995 21:47:27 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id VAA14075; Tue, 19 Sep 1995 21:44:30 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199509200444.VAA14075@phaeton.artisoft.com>
Subject: Re: Policy on printf format specifiers?
To: peter@taronga.com (Peter da Silva)
Date: Tue, 19 Sep 1995 21:44:29 -0700 (MST)
Cc: terry@lambert.org, peter@taronga.com, hackers@freebsd.org
In-Reply-To: <199509200128.UAA13444@bonkers.taronga.com> from "Peter da Silva" at Sep 19, 95 08:28:25 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: 482       
Sender: owner-hackers@freebsd.org
Precedence: bulk

> > 8-).  The complaint isn't
> > that you can't work around what is effectively a loss of information, but
> > that you have to do so.
> 
> What information loss is that?

How many records are in the file from stat information.

struct myrecord {
...
};

	...
	fstat( fs, &sb);
	records = sb.st_size / sizeof(struct myrecord);
	...

For one.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.