From:	alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Future of Allegro (?)
Date:	Sat, 16 Nov 1996 11:06:53 GMT
Lines:	36
Message-ID:	<848142410.4760.0@abwillms.demon.co.uk>
References:	<56eaj0$ap2 AT catapult DOT gatech DOT edu> <56g1ti$3ii AT ralph DOT vnet DOT net>
NNTP-Posting-Host:	abwillms.demon.co.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

bdarnell AT vnet DOT net (Ben Darnell) wrote:

>I volunteer to take over the maintainance.  I don't have time to add
>many new features, but I can upload new versions so we don't have to
>hear about bank.s anymore ;).  In fact, I'll be uploading a new
>version to x2ftp in a few minutes.  If anyone has any proposals for
>new features, email me.

A note here: Allegro includes it's own hardware interrupt handling.
Yet I've written libhw which does the same thing as a seperate,
generic, and perhaps even maybe better library. Now, libhw so far
seems stable on computers other than my own (fingers crossed), so it
might be a good idea at some point in the future to make Allegro use
libhw, for the simple reason that there's less duplication of code,
and if some nonstandard interrupt chip turns up in new motherboards,
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?


ABW
--

"Simply drag your mother in law's cellphone number from the
Address Book to the Laser Satellite icon, and the Targeting
Wizard will locate her. Then follow the onscreen prompts for
gigawattage and dispersion pattern..."

(Windows for Early Warning and Defence User's manual P385)

Alaric B. Williams Internet : alaric AT abwillms DOT demon DOT co DOT uk
<A HREF="http://www.abwillms.demon.co.uk/">Hello :-)</A>

- Raw text -