[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2006-03-18, Milan Mimica <milan.mimica@xxxxxxxxxx> wrote:
> Chris wrote:
> >
> >I'm almost positive it was.. at the very least they have name and desc
> >fields which you can use to get the name and description of the used
> >drivers. The setup program I'm quite sure does, or at least used to. I've
> >always gone under the assumption that these were available for use (I
> >mean, there's no need for name and description fields internally,
> >especially next to the unique 4-byte id field, and there's no other way to
> >get them).
>
> These are at the beginning of vtable so it shouldn't be a problem I guess.
Changing the DIGI_DRIVER and MIDI_DRIVER vtables are a bit of a problem
because some drivers are built as modules, so now 4.2.0 modules will
probably crash with 4.2.1.
Another problem is if somebody actually wrote a 3rd party driver module
and distributed it as a binary only, then we would have broken
compatibility. But I've never heard of anyone doing that.
Maybe we should start installing modules in /usr/lib/allegro/4.2.x
instead of /usr/lib/allegro/4.2 ?
Peter