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> |
Subject: | RE: An implementation of /dev/zero for DJGPP |
Date: | Mon, 25 Dec 2000 16:25:46 +0100 |
Message-ID: | <NEBBIOJNGMKPNOBKHCGHMEANCAAA.tim.van.holder@pandora.be> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
In-Reply-To: | <Pine.SUN.3.91.1001225130436.19455A-100000@is> |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
Importance: | Normal |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id KAA01083 |
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 |
> > extern int _djgpp_fsext_devices; > > int _djgpp_fsext_devices = __FSEXT_DEV_ZERO | __FSEXT_DEV_RANDOM; > > This will always link in the /dev/zero support. We are trying to avoid > bloating each program with code and data it will never use. My mistake - had overlooked the fact that the call to __FSEXT_add_open_handler() would pull in the rest of the functions as well. Suggestion withdrawn.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |