On Thu, 2 Oct 2003 10:13:53 +1000 (EST) Mark Livingstone <[EMAIL PROTECTED]> wrote:
ML> VZ> Basically, SWIG parses special .i files containing something looking like ML> VZ> C++ declarations and generates the glue necessary to call use the C++ ML> VZ> classes/functions from Python (and/or other languages, there is really no ML> ML> So it is a two way process? M <--> Python? Of course. We invoke Python hooks when soemthing interesting happens but for them to be able to do anything they should have access to our API. ML> VZ> ML> VZ> 2. try new SWIG (1.3.19?) which is supposed to be able to directly parse .h ML> VZ> ML> VZ> files and get rid of .i completely or, maybe, keep them but just for ML> VZ> ML> VZ> SWIG directives (i.e. we could tell it to ignore some methods or rename ML> VZ> ML> VZ> some others) ML> ML> OK. Given (realistically) that it is mostly going to fall to you to implement (any ML> other volunteers?) , how do you suggest we proceed? Well, actually I don't know why does it fall to me :-) Anybody could try to do this, it just needs some time. The first thing to do would be to simply try SWIG on our existing .h files. Probably it won't work, but I'm not even sure about it. Regards, VZ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
