[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] get volume
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Sat, 18 Mar 2006 07:19:08 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=L5YQh4OumDhZB7APsnziuwo+BrpRqAeT3G7AwglxFCshr4xjIS9C8nHiVYCecrpvrtsgqL4o76Is7/7As1j0t++3YQA0mQQqt8mMYC+2NEJVmbiHcll+60aoDlnrh1oOWKVDo10kQV1wUUHY0aqrWyf59LLekL4Lkgx5rM30FMQ=
On Saturday 18 March 2006 07:08, Elias Pschernig wrote:
> On Sun, 2006-03-12 at 10:51 +0100, Elias Pschernig wrote:
> > If we assume that a sound driver is only created and accessed by
> > Allegro, the patch can be applied as is, I think.
>
> I checked all the headers, and it seems digi_driver is never used in an
> inline or macro function. So, I committed it unmodified for now.
digi_driver, as well as midi_driver, gfx_driver, etc, are part of the public
API. I believe even on some platforms, the *_DRIVER structs are used as a
static array (eg. DIGI_DRIVER digi_driver_list[]), and changing the size of
them would then be a big nono.