Re: [Pyallegro] Questions about current implementation

[Grzegorz A. H. <gr...@ti...>]

On 2005-01-29, Juha-Matti Tapio <jm...@ve...> wrote:
> > What is the file allegro.c used for? I can rename it and the
> > alpy module is still built.
> 
> If my memory serves me right, it is the original module and it is
> not used anymore. allegro.py seems to be it's pair as they both
> carry the $Log$-notation which I used to prefer a few years ago.

You want to keep it?

> > And why at some point in alpy.py functions like get_allegro_id
> > or get_default_palette are deleted? Strikes me as odd that they
> > still are included in documentation.txt.
> 
> Everything is imported into alpy module's namespace by from _alpy
> import * earlier and the del-statements are propably meant to
> hide those imported definitions from the user. However most of
> these deletions are not necessary because those functions are
> wrapped in python-functions by the same name.

Hmmm... documentation generated by pydoc is beginning to look nice.

One thing I haven't looked yet, and you may save me the trouble,
is how is Allegro linked into alpy? Meaning, if I build alpy
against allegro 4.1.10 and then remove 4.1.10 and install 4.0.3,
would alpy import this version? Or once you build alpy, it is only
able to import the specific version it has been linked against?

Maybe 4.1.x vs 4.0.x was not a good example, because the ABI changes,
but what about 4.0.0 vs 4.0.3 then? If the library can change, alpy
will need version detection codes to modify the key constants. At
the moment I use a custom patch so that the shift key works for
4.1.18, because it's define changed at some point.