[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] New API ideas
- From: <spoofer255@xxxxxxxxxx>
- Date: Tue, 26 Apr 2005 09:40:58 +0200
- 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:content-disposition:references; b=Sj704yIupdmF3BA6TibQ6gwScJSSt+bYTGxg1kCrtQERhD788+K3R6kEEoGMxxEnBWCTHPS+XzC0PXtCB7k61bbyUIaJT2hdMoKCvvvADDY2pNaofwldEMtbEQ96HVLuLZoR02ExipS6gUlyOFuvEk0eNrBvFIZVebn2DPcNrJE=
> What are some things I should think about before
> submiting a patch for new API? I think my idea
> wouldnt need to be in any vtables, so thats not an
> issue. But are there any standards I should use? I
> already know about AL_METHOD but what else?
Read Allegro Hacker's Guide
(http://alleg.sourceforge.net/onlinedocs/en/ahack.html).
Look into Allegro source to see how it's done.