X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <250B3114DA16D511B82C00E0094005F8055AC7F1@MSGWAW11>
From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To: "'djgpp-workers AT delorie DOT com'" <djgpp-workers AT delorie DOT com>
Subject: RE: RFC - Dynamic loading
Date: Sun, 23 Dec 2001 13:00:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-2"
Reply-To: djgpp-workers AT delorie DOT com



> 
> Today there is no communications center between loaded DJGPP 
> applications, so if the first one in memory loads it, the next one has no 
> idea another  DJGPP image is even running.
> 
That's not an issue - we can develop such a interface

> 
> Almost all of our current library routines include static or
> global variables which are specific to the caller.  Much of 
> this should
> be restructured to be an "init" type code instead of all the bss_count
> stuff.
> 

Actually I'm not so concerned of turning libc into a dynamic library but
rather to have the ability of writing a
dynamic library which is loaded by a first djgpp program that uses it while
another programs would use the first copy
instead of loading their own ones.

Why is this for? 
I'm hoping I'll be finished with my Microsoft exams by March and I'm
planning to work on TCPIP library under Windows NT
Having a single instance of a TCPIP routines makes the whole design much
simpler ...