| delorie.com/archives/browse.cgi | search |
| From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
| To: | <djgpp-workers AT delorie DOT com> |
| Cc: | "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> |
| Subject: | Re: The Perl/FD issue: update |
| Date: | Mon, 24 Sep 2001 17:48:11 +0200 |
| Message-ID: | <000d01c14510$51197260$bd7d76d5@pandora.be> |
| MIME-Version: | 1.0 |
| X-Priority: | 3 (Normal) |
| X-MSMail-Priority: | Normal |
| X-Mailer: | Microsoft Outlook, Build 10.0.2627 |
| Importance: | Normal |
| X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4807.1700 |
| In-reply-to: | <Pine.SUN.3.91.1010924120559.25254E-100000@is> |
| 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 |
> Fixing this is a bit tricky. Hmm... Is there any reason for stdaux/stdprn to have FD's 3 and 4 specifically? If not, we could fopen() some dummy file (say, "/dev/stdaux", "/dev/stdprn", or whatever) at startup and use those FILE objects as stdaux/stdprn. That way, their FD will never clash with another FILE. This does not fix the other issue (calling close() on an FD currently open in a FILE) though.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |