Date:	Wed, 24 Jan 2001 10:22:14 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT bigfoot DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Where does gcc -o foo make foo.exe
In-Reply-To:	<3A6DA4D3.25820.8356D7@localhost>
Message-ID:	<Pine.SUN.3.91.1010124102157.25819Q-100000@is>
MIME-Version:	1.0
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

On Tue, 23 Jan 2001, Mark E. wrote:

> > In cygwin, I put it inside the code for write().  Nobody else uses it.
> 
> My problem comes from djgpp having write which calls _write and each takes 
> care of calling a fsext hook for write.

Sorry, I'm not following: why do fsext hooks interfere with this?  The
code which you are adding should run only if the handle is not hooked,
right?

Also note that `write' and `_write' call fsext hooks in orthogonal
cases.

- Raw text -