Date: Thu, 22 Nov 2001 11:23:52 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Amber N. Stange" <nicci AT eluviis DOT ohsu DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: djgpp 3.0.2 problem?
In-Reply-To: <3BFC9344.99DD5A43@eluviis.ohsu.edu>
Message-ID: <Pine.SUN.3.91.1011122112025.14166K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 22 Nov 2001, Amber N. Stange wrote:

> I can give you a good idea as to what your problem is.  Its using gcc
> 3x.
> gcc 3x is bugridden.  If you want the most hassle free time compiling
> and using Allegro I suggest you use 2.95.2 or 2.95.3

Ha!  There are some quite serious bugs in 2.95.x as well, just different 
bugs.

If you want stability in C programs and don't care about C++, GCC 2.7.2.1 
is your friend.

(Personally, I lament the trade-off of stability for development pace, 
that lately seems to be the trend in many packages.  People who preach 
for the realease-early-release-often paradigm tend to forget that the 
users might actually have something useful to do with the tools, instead 
of debugging the tools themselves.  Oh, well...)