[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] New API ideas
- From: thomas fjellstrom <tfjellstrom@xxxxxxxxxx>
- Date: Mon, 25 Apr 2005 19:34:34 -0600
- 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=fKkxo77JGvK/MR0Vki0juieY3D6lXkwe19KTQGVPYHZJ2G7SARA5W+eNXDY8V94WJhwyNWe+fMsHxG3JT4l0v18wEMXsYTzI5enamcbbiItK1Qzp3M08iocTMFd14eFEUhJDAqUwUoGsGnhbUvq6e1h01f54h0D6Ca3s5waUSxs=
On 4/25/05, Dustin Dettmer <dustin@xxxxxxxxxx> wrote:
> 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?
>
I think your best bet is to just look at whats already there, and do
it better ;)