From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Thu, 1 Mar 2001 15:40:06 -0500
MIME-Version:	1.0
Subject:	Re: O_TEMPORARY v3
Message-ID:	<3A9E6D56.14628.206ACC@localhost>
In-reply-to:	<7458-Thu01Mar2001215836+0200-eliz@is.elta.co.il>
References:	<3A9E3DF4 DOT 25576 DOT 8B4E27 AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer:	Pegasus Mail for Win32 (v3.12c)
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

> > !       {
> > !         fd = _creat(real_name, dmode);
> > !         if (fd != -1)
> > !           __set_fd_properties(fd, real_name, oflag);

> This is okay, but it means that an application cannot open an
> O_TEMPORARY file via _open or _creatnew.  Is that what we want?

Did you mean via _creat? I do have a call to __set_fd_properties in _open. I 
can add a call to __set....  in _creat, but I don't see how O_TEMPORARY can 
be passed to _creat when it doesn't take accept O_* flags.

- Raw text -