| 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: guilt <karthikkumar@xxxxxxxxxx>
- Date: Tue, 15 Mar 2005 14:51:37 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=bi9O2+HwnuLj7kKLuJ1x0cyxcnaZrUwb1+9oapJp0ezKs0K9qCYUxQzAD+mhv2F1IhTgXXkwrct7mbVxzZMCc19FW/kAS4P1mZmop7je6jpTHa4VhQbEzsEJOyAk4nCwRNYSBNr5HegwD8dNEqcPrUk2HlQrd0HPZdqNn6jKw0c=
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 :)
We can have major updates to Allegro this way by releasing only when
the core changes a lot.. :)
--
Karthik
http://guilt.bafsoft.net