Re: [Adonthell-devel] New structure status, thoughts, and problems

[Alexandre Courbot]

> - We could use the SWIG library, which is supposed to take care of such
> problems. But it would require the user to have it. Sucks a lot.

Eh, just checked SWIG's runtime library. You know what? The Python
runtime library just consists of a single, 16Kb large .c file that is
completely independant from the rest of SWIG. I don't think it would
hurt if we include it with Adonthell, make a nice shared lib with it,
and link our wrappers to it. Moreover it would reduce the overhead,
since there would only be one single shared copy of SWIG's runtime
library in memory (and not one per loaded module). Fair enough?

... actually it took 10 minutes to integrate it and run a test. It works
flawlessly, and adds no additional dependancy (just an additional lib
that resides in our "private" Adonthell libs directory). If no one
complains, let's run it that way!

The generic callback class design problem is still open, and comments
still welcome! Right now my example is working - I can call a Python
callback every time a key is pushed, but have no way to know which key
has been pushed, as I don't have any arguments passing.

Oh, would you like to see the code? I can put it somewhere, even though
it's not completely finalized, but it should compile everywhere and
there is doxy doc too.

Alex.
-- 
http://www.gnurou.org