X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Sat, 08 Jan 2005 22:09:40 +0200
From: "Eli Zaretskii" <eliz AT gnu DOT org>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-ID: <01c4f5be$Blat.v2.2.2$21b025c0@zahav.net.il>
Content-Transfer-Encoding: 7BIT
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 2.2.2
In-reply-to: <BBVDd.54479$nP1.21957@twister.socal.rr.com>
	(sam124 AT operamail DOT com)
Subject: Re: Shared libraries?
References:  <BBVDd.54479$nP1 DOT 21957 AT twister DOT socal DOT rr DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Samuel Lauber" <sam124 AT operamail DOT com>
> Date: Sat, 08 Jan 2005 18:26:41 GMT
> 
> COFF has supported shared libraries for a LONG time. I think DJGPP should
> have shared library support.

What for?  There could be only one DJGPP process running in each VM,
so the principal benefit of shared libraries--sharing code across
multiple executables--does not exist.  And with the ridiculously low
costs of today's disks, the size of the executable on disk doesn't
matter much anymore.

> Sure, DJGPP has emu387.dxe, but those DXEs are hard.

You are welcome to work on lifting some of the limitations of DXE, it
would be better than starting shlib support from scratch.