From:	sparhawk AT eunet DOT at (Gerhard Gruber)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Making Libraries
Date:	Sun, 05 Jul 1998 18:01:14 GMT
Organization:	Customer of EUnet Austria
Lines:	34
Message-ID:	<35a5b661.3601985@news.Austria.EU.net>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980705163518 DOT 23984c-100000 AT is>
NNTP-Posting-Host:	e198.dynamic.vienna.at.eu.net
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Destination: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
From: Gruber Gerhard
Group: comp.os.msdos.djgpp
Date: Sun, 5 Jul 1998 16:35:36 +0300 (IDT):

>This thread was about overlays, not sharted libraries.  With overlays,
>you cannot produce them once and then use them with many programs.
>Every program needs its own overlays.

Sorry! Never used overlays, so I forgot about this one.

>In a less ideal situation, such as the one which exists with Windows
>programs, the different and incompatible versions of the same DLLs
>make an enormous mess, and are one of the main causes for frequent
>crashes of end-user machines.  If you want to be sure your programs
>will not crash and burn on the machine of John Doe the user, in
>practice you need to distribute the shared library with the
>executable, which all but defeats the purpose of the shared libraries.

That's rather a problem with the typicla DOS programmer. As I see it Windows
Programmers are often people who came from DOS. and in DOS there was no realy
discipline in programming. Unix supports shared libraries and there are nor
real problems. If you need the same library with a different version, then you
can create links or change the environment and everything works fine. DOS
programmes tend to fix their path and environment and don't let the user much
choice about what he wants to stick where.
--
Bye,
   Gerhard

email: sparhawk AT eunet DOT at
       g DOT gruber AT sis DOT co DOT at

Spelling corrections are appreciated.

- Raw text -