This might be somewhat interesting:
http://blogs.msdn.com/jmstall/archive/2007/01/06/Typesafe-GetProcAddress.aspx
Of course, it might entail certain security permissions, so may not be useful
in certain cases.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Slide
Sent: Sunday, January 07, 2007 5:53 AM
To: Discussion of IronPython
Subject: Re: [IronPython] C Extensions
On 1/7/07, Sanghyeon Seo <[EMAIL PROTECTED]> wrote:
> 2007/1/7, slide <[EMAIL PROTECTED]>:
> > 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?
>
> If I understood correctly, Phalanger (PHP implementation for .NET) does
> something similar to support PHP's C extensions, so I think it's certainly
> possible. That doesn't mean it would be easy in any way.
>
> No, I don't have slightest idea how to implement it.
>
> --
> Seo Sanghyeon
It looks like Phalanger uses CLI/C++ to interact with C/C++
extensions. At this point that would restrict its usage to Windows,
but I guess it might be a good start.
slide
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
