| www.delorie.com/archives/browse.cgi | search |
| From: | "Mark E." <snowball3 AT bigfoot DOT com> |
| To: | DJ Delorie <dj AT delorie DOT com>, djgpp-workers AT delorie DOT com |
| Date: | Mon, 12 Jun 2000 23:18:45 -0400 |
| MIME-Version: | 1.0 |
| Subject: | Re: tmpfile in DJGPP |
| Message-ID: | <39456FD5.25841.36AF6@localhost> |
| In-reply-to: | <200006130301.XAA02001@envy.delorie.com> |
| References: | <39454330 DOT 19416 DOT 704D85 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 |
> 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. True enough. Perhaps we should stick to considering how to handle properly- written programs that make use of temporary files like Bash.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |