RE: [AL] Namespace Problems

[Omar C. <co...@no...>]

> al_clear(BITMAP*);
> 'alleg' is too long for prefixing, 'allg' is ugly, but 'al_' is just right.
>  alClear(BITMAP*) - A possibility? The bicaps look weird though.

The later would make transition more difficult.
I am entirely for 'al_'.

> Or we could do what DX does - stick all of the functions into a big
> struct with function pointers for those using C, otherwise a big
> class for those using C++. This instantly resolves namespace issues.
> Also, other things like initializing the lib can be done automatically
> in the constructor, etc. 

Automatic Allegro initialization is something I *NEED* to avoid, and 
probably several large problems too. In my program, I'm doing lots of 
things before actual Allegro initialization and usage, and sometimes,
I don't need it at all.

> I personally would prefer it if we could go the latter route, because
> then multiple allegro objects could exist all at once, too, although I
> don't know how that would be useful :)

I don't know either! :)