Date:	Mon, 13 Sep 1999 13:43:56 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Mike Gee <medline AT creator DOT dp DOT ua>
cc:	djgpp AT delorie DOT com
Subject:	Re: DJGPP wont compile C++ programs
In-Reply-To:	<01befbcf$46d02240$LocalHost@mike>
Message-ID:	<Pine.SUN.3.91.990913134327.8923M-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 10 Sep 1999, Mike Gee wrote:

> Yes, but I still think that transient bug workarounds like this unfamous
> RHIDE bug should somehow be separated from fundamental questions that aren't
> likely to change with next minor version.

I don't know how to tell the former from the latter.  Since DJGPP is
developed by volunteers on their free time, there's no way of knowing
when, and indeed if, a particular bug or misfeature will be fixed.

> It seems to me that this particular RHIDE bug has one-line fix. I wonder does
> nobody cared to mail RHIDE author about it? As I understand, this bug is
> almost one year old and counting, as long as RHIDE 1.4 is recommended by DJ
> zip-picker. Is it really that hard to add one file to distribution? Not that
> I'm whining (or am I?), I just don't know the proper procedures. Allegro went
> from 3.11 to 3.12 very quick, when the problem with building it with gcc-2.9
> arised.

Different people have different amounts of free time and different
priorities.  AFAIK, Robert Hoehne was busy with improving GDB lately,
which is no less important for RHIDE, as RHIDE's debugging engine is
based on GDB.

> BTW what are legal requirements on FAQ-derivated works? e.g. when writing my
> own DJGPP reference, how can I use FAQ information in it? 

You can use it freely.  See chapter 23 for a few words I have to say
about this issue.

- Raw text -