| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-workers-bounces using -f |
| From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
| To: | <djgpp-workers AT delorie DOT com> |
| Subject: | Re: RFC - Dynamic loading |
| Date: | Thu, 20 Dec 2001 21:35:48 +0100 |
| Message-ID: | <000001c18995$e8d5e970$c27d76d5@pandora.be> |
| MIME-Version: | 1.0 |
| X-Priority: | 3 (Normal) |
| X-MSMail-Priority: | Normal |
| X-Mailer: | Microsoft Outlook, Build 10.0.2627 |
| Importance: | Normal |
| In-Reply-To: | <20011220124507.A26821@kendall.sfbr.org> |
| X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2462.0000 |
| 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 |
> What do you guys mean by these existing packages being too `heavy'? > Too much code to add to libc? Is the standard dlopen interface > just overkill for djgpp? There's that, and then there's the point that the dynamic-loading code should be as self-contained as possible (so most of libc can become a shared library). Since DLX (and my derivation) are C++-based, there's no way it can satisfy that last condition.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |