Date: Mon, 12 Jun 2000 23:01:07 -0400
Message-Id: <200006130301.XAA02001@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <39454330.19416.704D85@localhost> (snowball3@bigfoot.com)
Subject: Re: tmpfile in DJGPP
References: <39438707 DOT 29061 DOT 505C1E AT localhost> <39454330 DOT 19416 DOT 704D85 AT localhost>
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


> The objective, as I see it, is to provide a reliable way to port
> Unix code that uses the 'open/unlink/close' way of making a
> temporary file.

I don't think there *is* a reliable way of doing this, especially when
you consider parent/child processes.  Consider a parent that has a
file open, and it spawns a child that deletes the file.  We can't trap
that.