Date: Sun, 24 Oct 1999 09:34:20 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bug in fsetpos()?
In-Reply-To: <199910212124.RAA11174@mccoy2.ECE.McGill.CA>
Message-ID: <Pine.SUN.3.91.991024093353.29385M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 21 Oct 1999, Alain Magloire wrote:

> I don't think this is a bug, fsetpos() returns 0 if it succeeds otherwise
> it returns a non-zero value and sets errno to indicate the error.

Right.  But if fseek returns -1, that surely counts as a failure,
right?  So ignoring the return value of fseek *is* a bug, since that
makes fsetpos return zero when in fact it failed.