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:25:52 GMT
Organization: The University of Texas at Austin, Austin, Texas
Lines: 17
Message-ID: <36239843.37669784@newshost.cc.utexas.edu>
References: <3622729c DOT 417426724 AT newshost DOT cc DOT utexas DOT edu> <36235C46 DOT 8C452D20 AT arx 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 15:57:26 +0200, Black Phantom <vadim AT arx DOT com>
wrote:

>The whole thing is utterly inefficient since dynamic linking was
>designed for sharing one copy of library among different address spaces.
>In DOS there is a single-tasking environment so DLL system will eat up a
>lot of memory, saving nothing. What do you need it for, what is the
>design goal?

Perhaps what I was looking for was more along the lines of a device
driver, rather than a DLL (is there a difference?). At first I wanted
to be able to read/write different file systems by writing seperate
external modules with common functions like WriteToDisk and
ReadFromDisk. Then, of course, by knowing which FS was in use, I would
simply choose which module to use.

- Hicks