Date: Wed, 11 Mar 1998 11:43:33 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>
cc: DJ Delorie <dj AT delorie DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: mkstemp made safer
In-Reply-To: <35064D94.4D3236EA@taniwha.tssc.co.nz>
Message-ID: <Pine.SUN.3.91.980311114116.7344X-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 11 Mar 1998, Bill Currie wrote:

> > + file in DENY_ALL mode.
> > + @findex mkstemp
> 
> Is this correct, or does SH_DENYRW mean DENY_ALL?  It looks like they
> mean the same thing, but I want to be sure.

They are the same.  I'm used to use DENY_ALL, but the headers define 
SH_DENYRW.  If I'm the only one who uses DENY_ALL as a matter of speech, 
please tell me and I will change the docs.

> Anyway, thanks Eli.  Although it's been a while, it was painfull only
> being able to have one gcc compile going at a time under windows.

I would be interested to know if somebody links gcc with these patched 
versions and sees that several compilations can now run at the same 
time.  I myself didn't try that yet.