delorie.com/archives/browse.cgi | search |
Date: | Sun, 11 Jun 2000 17:32:47 -0400 |
Message-Id: | <200006112132.RAA22801@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <39438707.29061.505C1E@localhost> (snowball3@bigfoot.com) |
Subject: | Re: tmpfile in DJGPP |
References: | <39338C80 DOT 9048 DOT 8606D AT localhost> from "Mark E." at "May 30, 2000 09:40:16 am" <39438707 DOT 29061 DOT 505C1E 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 |
> I'd like to have a consensus on the right interface(s) to give an fd the > 'remove-on-close' attribute before starting again on this. My original > proposal if I remember correctly was for a 'O_TEMPORARY' or > 'O_REMOVE_ON_CLOSE' attribute that would be passed to open(). > > Also, Win32's CreateFile has a flag to mark a file handle as 'remove-on- > close'. If anyone knows of a Win32 libc that exposes this feature, please > speak up. MSVC uses _O_TEMPORARY (but they use _O_CREAT, _O_ORDONLY, etc) so O_TEMPORARY is probably OK for us.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |