From owner-freebsd-hackers  Tue Jan 30 20:47:41 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA13019
          for hackers-outgoing; Tue, 30 Jan 1996 20:47:41 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA13002
          for <hackers@freebsd.org>; Tue, 30 Jan 1996 20:47:16 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA14046; Wed, 31 Jan 1996 15:44:04 +1100
Date: Wed, 31 Jan 1996 15:44:04 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199601310444.PAA14046@godzilla.zeta.org.au>
To: hackers@freebsd.org, mrcpu@cdsnet.net
Subject: Re: Maybe bug in fsetpos?
Sender: owner-hackers@freebsd.org
Precedence: bulk

>On the BSD/OS list there's mention of a wrong type to the second 
>parameter in the fsetpos function.

>I didn't look at it, but in FreeBSD it's a long, and the BSD/OS patch 

Nope.

>makes it a quad_t or something like that.  

>My question is if the parameter is wrong in freebsd's fsetpos.c...

The second arg to fsetpos() has always had type `const fpos_t *'
(ANSI standard) in FreeBSD.  fpos_t had type long in FreeBSD-1.x.
It has type `long long' in FreeBSD-2.x.  Portable applications
shouldn't notice the difference.

Bruce