delorie.com/archives/browse.cgi | search |
From: | Jeramie DOT Hicks AT mail DOT utexas DOT edu (Jeramie Hicks) |
Newsgroups: | comp.os.msdos.programmer,alt.msdos.programmer,comp.os.msdos.djgpp |
Subject: | Re: DOS-based DLL system |
Date: | Tue, 13 Oct 1998 18:35:53 GMT |
Organization: | The University of Texas at Austin, Austin, Texas |
Lines: | 15 |
Message-ID: | <36239be6.38601254@newshost.cc.utexas.edu> |
References: | <3622729c DOT 417426724 AT newshost DOT cc DOT utexas DOT edu> <36235C46 DOT 8C452D20 AT arx DOT com> <362393DA DOT AE33780A AT inetlab DOT com> |
NNTP-Posting-Host: | resnet-23-244.dorm.utexas.edu |
X-Newsreader: | Forte Free Agent 1.11/32.235 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
On Tue, 13 Oct 1998 23:54:34 +0600, Ilya Ryzhenkov <orangy AT inetlab DOT com> wrote: > so you can simply alloc some memory, load DLL image into it, then get symbol address >(somehow - depends on the DLL layout and your goals) and call the pointer. That is >how it was done in Windows DLL system - you ask to load dll, then ask for >pointer to function and then just call it via pointer. That was the basic idea I had in mind. Something utterly simple. The toughest part I see is peeking into the DLL to retrieve the function locations on loading, plus handling any parameters. I wouldn't need global variables or anything, because I can't imagine these functions being passed more than a few parameters anyway. - Hicks
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |