Date: Sat, 11 Aug 2001 01:33:39 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: arch@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: CFR: fseek<0 + feof error (with fix) Message-ID: <20010811013339.A16759@nagual.pp.ru> In-Reply-To: <20010811010820.A16395@nagual.pp.ru> References: <20010810232939.A14964@nagual.pp.ru> <20010810234922.A15324@nagual.pp.ru> <200108102100.f7AL03x37506@khavrinen.lcs.mit.edu> <20010811010820.A16395@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 11, 2001 at 01:08:22 +0400, Andrey A. Chernov wrote: > On Fri, Aug 10, 2001 at 17:00:03 -0400, Garrett Wollman wrote: > > > > No, [EOVERFLOW] is for Large File Summit support. > > Of course for it too, but it is the other end of the valid range. > > As it says, "the resulting file offset would be a value which cannot be > represented correctly" and it cannot be, because range overflow occurse in > the calculation process, not given directly in arguments, as for EINVAL. Well, from second thought, it will be better to leave EINVAL there, as in my initial variant. EINVAL describes exact negative offsets while my EOVERFLOW quoute is out of context which speak about ofsset representation fit in long or off_t space. Your interpretation of EOVERFLOW is not so right too, there is E2BIG for this reason in fseek errors descriptions. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010811013339.A16759>