From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Sat, 17 Mar 2001 16:24:07 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: zero fill the eof gap 2
Message-ID: <3AB38FA7.12892.36DDAA@localhost>
In-reply-to: <5567-Sat17Mar2001095108+0200-eliz@is.elta.co.il>
References: <3AB26D06 DOT 10811 DOT 1650EF AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> That's probably true, but imagine a case where an FSEXT doesn't want
> to handle the _write call, but does handle an lseek call.  I think in
> this case, the FSEXT will be called via lseek.  Is that a problem?

I don't foresee one in this case. When the FSEXT opens a real file, handles 
lseek, and wants the zero fill behavior then it will have to set the flag 
itself. Otherwise, no special handling is required.

Mark