Re: [AD] Allegro generalization/extension mechanism

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]

To: alleg-developers@xxxxxxxxxx
Subject: Re: [AD] Allegro generalization/extension mechanism
From: AJ <aj@xxxxxxxxxx>
Date: Wed, 16 Mar 2005 16:02:05 +1100

guilt wrote:

So, this was the only point: only when it comes to releases, the
developer who wants the PNG code needn't wait for the next "stable"
update of the whole base to get his hands on.. the newer stable
release of the code will be available for download :)



CVS is always available.

We can have major updates to Allegro this way by releasing only when
the core changes a lot.. :)


the average user gets very confused by this.

Follow-Ups:
- Re: [AD] Allegro generalization/extension mechanism
  - From: guilt

References:
- [AD] Allegro generalization/extension mechanism
  - From: guilt
- Re: [AD] Allegro generalization/extension mechanism
  - From: Chris
- Re: [AD] Allegro generalization/extension mechanism
  - From: guilt
- Re: [AD] Allegro generalization/extension mechanism
  - From: Evert Glebbeek
- Re: [AD] Allegro generalization/extension mechanism
  - From: guilt
- Re: [AD] Allegro generalization/extension mechanism
  - From: guilt

Messages sorted by: [ date | thread ]
Prev by Date: Re: [AD] Add timeBeginPeriod(1) to wtimer.c
Next by Date: Re: [AD] Allegro generalization/extension mechanism
Previous by thread: Re: [AD] Allegro generalization/extension mechanism
Next by thread: Re: [AD] Allegro generalization/extension mechanism

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/