> 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 work) rather than compiling empty stub functions and > trying to overload the symbols at (load/run)time.
I agree: write a Cython wrapper that includes generic C functions that call the methods of a Cython object; then provide inheritance of that object to overload the functionality. Nick --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
