On Tue, Aug 25, 2009 at 10:52 PM, Robert Bradshaw<[email protected]> wrote: > I have to say the one thing I don't like about weave is its use of > strings to contain opaque code. OK, there's two things--the context > switch between C and Fortran and Python. Nonetheless, I can see how > it's really handy and a clever hack. I really want to avoid Cython > allowing snippets of C and Fortran scattered in valid Cython sources > if at all possible. (I would not be opposed to a cython.eval or > cython.exec that would invoke the complier on a string).
I should add that I'm not asking for *the* weave approach, just for that overall level of functionality and flexibility. When weave was written, nothing like cython's underlying machinery was even in the horizon, so weave was already a phenomenal tool to have. But if the equivalent functionality can be built, more cleanly on top of cython, great! I'm just trying to provide you guys with context on the kinds of things I've used weave for in the past and found it useful, not to push for any particular implementation details. Regards, f _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
