Simon Burton wrote:
I would like to expose some functions as external
symbols when i build a .so
def foo(i, j):
return i+j
foo._expose_ = [rffi.INT, rffi.INT]
well, the above code would produce:
extern int foo(int i, int j)
{
return i+j;
}
(and perhaps an
well, the above code would produce:
extern int foo(int i, int j)
{
return i+j;
}
(and perhaps an accompanying .h file)
thereby providing an interface for other C programs.
This is rffi producing rather than consuming a C interface.
Simon.
Hey Simon.
It's doable, and not
On Tue, 07 Aug 2007 14:15:48 +0200
Maciek Fijalkowski [EMAIL PROTECTED] wrote:
Simon Burton wrote:
On Fri, 3 Aug 2007 12:14:13 -0700
Simon Burton [EMAIL PROTECTED] wrote:
I would like to expose some functions as external
symbols when i build a .so
def foo(i, j):
return
Simon Burton wrote:
On Fri, 3 Aug 2007 12:14:13 -0700
Simon Burton [EMAIL PROTECTED] wrote:
I would like to expose some functions as external
symbols when i build a .so
def foo(i, j):
return i+j
foo._expose_ = [rffi.INT, rffi.INT]
It seems like this could also enable a
On Fri, 3 Aug 2007 12:14:13 -0700
Simon Burton [EMAIL PROTECTED] wrote:
I would like to expose some functions as external
symbols when i build a .so
def foo(i, j):
return i+j
foo._expose_ = [rffi.INT, rffi.INT]
It seems like this could also enable a plugin system for rpython,
and
I would like to expose some functions as external
symbols when i build a .so
def foo(i, j):
return i+j
foo._expose_ = [rffi.INT, rffi.INT]
This is basically so I can write cpython extension modules in rpython.
(and manually doing ref counting (etc.) on the cpython objects.)
Simon.
