X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: updating older programs' stubs (advantages? disadvantages?)
Date:	Sat, 20 Jan 2007 23:32:23 CST
Organization:	Rice University, Houston, TX
Lines:	22
Message-ID:	<45b2fae7.sandmann@clio.rice.edu>
References:	<1169071616 DOT 021221 DOT 133750 AT m58g2000cwm DOT googlegroups DOT com>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1169358055 4686 128.42.105.3 (21 Jan 2007 05:40:55 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	Sun, 21 Jan 2007 05:40:55 +0000 (UTC)
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Since DJGPP-compiled stuff is quite popular, I'm just curious: would
> there be any known advantages/disadvantages to updating the stubs of
> these older programs? In other words, what (if any) functional
> differences are there between, say, the v2.00T (1996) stub and the
> v2.02T (2001) stub (or even compared to the DJGPP 2.04 beta's 2003,
> v2.04T stub)?

Taking a quick look in CVS, the differences I see between v2.00 and
v2.02 are:

Fixed spelling in notice
Updated version
Increased default stack size from 256K to 512K
Added return error codes
Size optimizations
Handle empty paths
Close handles for child processes if parent has too many open
Improved error messages

So - nothing critical, but a stub upgrade shouldn't hurt and might fix
a rare problem.

- Raw text -