Date: Sat, 17 Jun 1995 05:11:47 +0400 (MSD) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= aka "Andrey A. Chernov, Black Mage" <ache@astral.msk.su> To: Terry Lambert <terry@cs.weber.edu> Cc: hackers@freebsd.org, peter@haywire.DIALix.COM Subject: Re: penalty of using off_t for arithmatic with gcc's long Message-ID: <MUJlYule90@astral.msk.su> In-Reply-To: <9506161732.AA12315@cs.weber.edu>; from Terry Lambert at Fri, 16 Jun 95 11:32:22 MDT References: <9506161732.AA12315@cs.weber.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <9506161732.AA12315@cs.weber.edu> Terry Lambert writes: >> 1) fseek argument: it is "long" per POSIX standard. You can't >> read > 2GB in POSIX enviroment in any case with 4bytes longs >> using fseek. >This is not true. The off_t typedef "must be an atomic type" per >POSIX. 1) I say nothing here about atomic off_t, I say about "long" type of fseek argument, you can see it in any POSIX docs copy. 2) In my POSIX specs (maybe I look at wrong place?) I don't read that off_t must be atomic, it says "integral". >> If you include <unistd.h>, you don't need to cast lseek() argument to off_t. >Because the prototype hides the bogosity from you ...a bad thing if you >move the code between non-POSIX/non-ANSI 100% compliant systems -- like >BSD. BSD just doesn't have this particular non-compliance bogosity, >which doesn't guarantee that it doesn't have others. My NN patch make it works even without prototype hiding using correct variable/cast types directly. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MUJlYule90>