[IronPython] C Extensions

Slide slide.o.mix at gmail.com
Mon Jan 8 16:09:43 CET 2007


I think the main issue with C extensions, is that they call back into
the Python runtime library to register themselves, this would have to
be intercepted by FePy in order for things to work correctly.

slide

On 1/8/07, dwelden <dwoogle at gmail.com> wrote:
> SWIG can generate wrappers for C#. Perhaps that could form the
> foundation for C module wrapping for FePy.
>
> On Jan 6, 7:58 pm, slide <slide.o.... at gmail.com> wrote:
> > As it has come up on the list several times, I was wondering if anyone
> > had given any thought to implementing an interface such that C
> > extensions could be used with FePy I know that FePy would have to
> > implement and export (and do some other magic) the C registration
> > functions, etc that the C extensions call. On Windows specifically, I
> > can envision that the import table of the C extension would need to be
> > modified to not rely on libpython, as well as redirecting the addresses
> > of the imported Python API functions to FePy functions which do the same
> > thing, seems somewhat complicated to me. Is it even feasible to do?
> >
> > slide
> >
> > _______________________________________________
> > users mailing list
> > u... at lists.ironpython.comhttp://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> _______________________________________________
> users mailing list
> users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>



More information about the Ironpython-users mailing list