[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: RE: [AD] About 4.3
- From: Victor <vwss1984@xxxxxxxxxx>
- Date: Wed, 7 Dec 2005 09:01:05 -0300 (ART)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=c3ou+nfP3fOEWwDUjHkgFoDEysPg3zL38G3rZWRmn5CeGQ8EbUCnNFVOMtwqpCpML107mV13OwakpqBJlkP42tyjay2HFOxPCPkXFahQl0jhRIeJp9kTLMGpgKUy7lInU8z77a5H40Xvusq4MWZ0i+As5r4uW1r/OAJjUaotR7o= ;
--- Vincent Penecherc'h <Vincent.Penecherch@xxxxxxxxxx> wrote:
> > Wholesale al_ prefixing is not going to happen, as we've said
> before.
> > Only the new API gets the al_ prefixes.
>
> Will there be al_ prefixed aliases though ?
> Kinda like the alcompat.h file ?
>
Sorry about the intromission, but in my humble opinion:
Some places really need the al_ prefix, to make it clear that is a
allegro function, macro or whatever or avoid conflicts with other
things, but if we prefix everything with _al the 4.3 API will look like
al_hungary_notation which is horrible. And this deprecates symbols
without any good reason ("we just decided rename it" isn't a good
reason).
Victor Williams Stafusa da Silva
_______________________________________________________
Yahoo! doce lar. Faça do Yahoo! sua homepage.
http://br.yahoo.com/homepageset.html