Date: Mon, 09 Nov 1998 12:06:12 -0800 From: Mike Smith <mike@smith.net.au> To: Dan Nelson <dnelson@emsphone.com> Cc: Thomas David Rivers <rivers@dignus.com>, freebsd-hackers@freefall.cdrom.com Subject: Re: A stdio question... does fpos_t really need to be 'long long'? Message-ID: <199811092006.MAA00487@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 09 Nov 1998 11:09:55 CST." <19981109110955.A5248@emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> In the last episode (Nov 09), Thomas David Rivers said: > > Ok - here's a question for the stdio internal gurus... > > > > ftell() is defined to return a 'long' (32 bits). > > fpos_t is defined as a 'long long' (64 bits). > > fgetpos() accepts an fpos_t as it's second argument, and is > > implemented as: > > > > retval = (*pos = ftell(fp)) == (fpos_t) -1; > > return (retval); > > > > If this is the case... then why is fpos_t a 'long long'? If, in > > fact, it can never be set that large? > > I noticed this back in April and commented on it. I believe the > consensus was that fsetpos()/fgetpos()/fseek()/ftell() should be > wrappers for the X/Open functions fseeko() and ftello(), which take > off_t arguments. > > Unfortunately, I never submitted patches, and neither did anyone else. > > -Dan Nelson > dnelson@emsphone.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message So submit them, dammit! 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811092006.MAA00487>