From: bdarnell AT vnet DOT net (Ben Darnell)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Future of Allegro (?)
Date: Sun, 17 Nov 1996 02:28:44 GMT
Organization: Vnet Internet Access, Inc.
Lines: 23
Message-ID: <56lt90$t7i@ralph.vnet.net>
References: <56eaj0$ap2 AT catapult DOT gatech DOT edu> <56g1ti$3ii AT ralph DOT vnet DOT net> <848142410 DOT 4760 DOT 0 AT abwillms DOT demon DOT co DOT uk>
NNTP-Posting-Host: vts-char4-s22.vnet.net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams) was overheard
mumbling incoherently about Re: Future of Allegro (?):

>there's only one set of sources to change. OTOH, libhw expects a
>patched gcc, and Allegro is fine on normal gcc. Making Allegro use
>libhw and thus expect patched gcc will be a problem for those people
>who would find it hard to get a patched gcc (2400 baud modem etc!).

>Any thoughts?

I think requiring a patched gcc for Allegro would be a bad idea, since
a surprising number of people get Allegro without even getting make
(and then bug us about it here ;)

Also, it could get confusing if other patches for gcc become available
(eg the Pentium optimization patch)

     __                         __
 /> /_ /| /   /\  /|  />  /| / /_ /  /
/> /_ / |/   /_/ /-| / \ / |/ /_ /_ /_
http://users.vnet.net/bdarnell
bdarnell AT vnet DOT net