[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 2006-03-18 at 07:19 -0800, Chris wrote:
> 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.
>
Well, I wouldn't say public API, more internal API - else it would need
to get documented.
And so, in this case, I doubt there's any code accessing them directly,
so it should be safe. But well, I didn't test it or think too much about
it.. and I can revert it easily.
--
Elias Pschernig