| Re: [AD] Alleg5 - new driver structure idea |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Bob wrote:
> Pros:
> - Easy to add "drivers" for just about every component of Allegro
> (mixer, bitmap loader, graphics, etc)
[snip]
> So, in your opinion, is this good/bad/overkill, and why?
Looks good to me at first sight, and the argument that it makes it
easy for add-ons to register drivers is a good one, I think. I do
wonder about a few things though, but I don't have enough
allegro-internal knowledge about that:
- how will allegro know which function to call? Does it have to do a
string lookup on the driver ID to find the graphics functions, and
then a string lookup to find the 'blit' function, for example? I
assume not, but I don't see how that would work with the indicated
structure. Do you want to have fixed array indices to access a
certain driver / function pair?
- how bad is the 'internal bloat' compared to what we currently have?
Hein Zelle
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<
Unix is user friendly. It's just very particular about who
it's friends are.
Hein Zelle hein@xxxxxxxxxx
http://www.icce.rug.nl/~hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<