Xref: news2.mv.net comp.os.msdos.djgpp:6178
From: <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GO32 stuff
Date: Fri, 19 Jul 1996 15:51:40 CDT
Organization: Rice University, Houston, Texas
Lines: 14
Message-ID: <31eff495.sandmann@clio.rice.edu>
References: <4sobl5$b01 AT news DOT mpu DOT com> <Pine DOT SOL DOT 3 DOT 91 DOT 960719185219 DOT 19581F-100000 AT zveris> <Pine DOT SOL DOT 3 DOT 91 DOT 960719192434 DOT 19781A-100000 AT zveris>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>  WILL?? Does that mean my [nearptr] idea will make it into DJGPP? 

No guarantees - it has to be coded, tested, be backward compatible, and
someone has to find the time to do it.  Then the "djgpp-developers"
cabal gets to tinker with it and if DJ likes it it appears in some
future release :-)

>   GO32's obsolete, right? I assume then that all __go32.. stuff in libc is
> just for compatibility with V1. 

I would agree that they should probably be renamed __djgpp instead, with a
#define for compatibility purposes.  But things like that are pretty
low on developer's priority lists (bug fixes/needed new functionality
are always first).