Subject: RE: lseek past EOF doesn't append zeros under Windows 95
From: [email-masked] (Sergey Okhapkin)

20 Jun 1998 20:42:54 -0700
Message-ID: <01BD9C8B.7D1AD6A0.cygnus.gnu-win32@sos>
To: "[email-masked]" <[email-masked]>,
        "'David Fox'"
	 <[email-masked]>
Cc: "[email-masked]" <[email-masked]>

David Fox wrote:
> The documentation for lseek states
> 
>        The lseek function allows the file offset to be set beyond
>        the  end  of the existing end-of-file of the file. If data
>        is later written at this point, subsequent  reads  of  the
>        data in the gap return bytes of zeros (until data is actu-
>        ally written into the gap).
> 
> but under Windows 95 the cygwin32 package does not behave this
> way.  The gap is filled with garbage.  One package that depends

It's a well-known bug of Windows 95. Cygwin doesn't care about gaps, it's the task of underlying OS. The problem doesn't exists on NT.

-- 
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".