Date: Sun, 09 Mar 1997 11:48:57 +1200
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: File system extensions -- write() doesn't work?
To: James McCann <jmccann AT junkmailwolfenet DOT com>
Cc: djgpp AT delorie DOT com
Reply-to: billc AT blackmagic DOT tait DOT co DOT nz
Message-id: <3321FAE9.1A91@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <331F8657 DOT 68B1707 AT junkmailwolfenet DOT com>

James McCann wrote:
> 
> The attached program shows  behavior I did not expect.  It installs
> a handler for file descriptors returned by __FSEXT_allocate_fd and
> installs the handler w/ FSEXT_set_function.  When the write function
> is called, the handler is called only for the first write.  Read and
> close work as expected, and if the write() calls are replaced w/ calls
> to _write(), the handler is called as expected.  I am using the libc.a
> from djdev201.zip dated 10/31/96.
> 
> Is this a bug, or am I doing something wrong?

Might be a bug (dunno).  When I was browsing the source code to libc to
check out the limitiations of FSX, I found a few problems, one of which
was write() wouldn't work properly with binary(or text?) files. There
where a few other instances where I though the fsx routines should have
been called but weren't.

I'll dig out my notes again sometime soon and post a format bug report
(maybe even a fiz).

Bill
-- 
Leave others their otherness.