On Apr 2, 2009, at 8:22 PM, Chris Swierczewski wrote:
> Robert,
>
>> So I understand you better, what you're trying to do is let the user
>> provide their functions at runtime rather than at compile time?
>
> Yes.
>
>> I think the easiest way to go about this would be to provide
>> custom non-
Robert,
> So I understand you better, what you're trying to do is let the user
> provide their functions at runtime rather than at compile time?
Yes.
> I think the easiest way to go about this would be to provide custom non-
> empty functions that call your code (e.g. via a function pointer the
Also, would Cython C API Declarations be another possible soution?
http://docs.cython.org/docs/external_C_code.html?highlight=compile#c-api-declarations
--
Chris
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe
> So I understand you better, what you're trying to do is let the user
> provide their functions at runtime rather than at compile time? I
> think the easiest way to go about this would be to provide custom non-
> empty functions that call your code (e.g. via a function pointer the
> way callbacks
On Apr 2, 2009, at 12:55 PM, Chris Swierczewski wrote:
> Is there a way to overload or redirect from symbols in a compiled
> library to a Cython function?
This is more of a C/fortran question than a Cython one (your cdef
Cython functions are just plain C functions) and I believe the answer
i
