To me, the problem with using Cython with F2PY extensions is that Cython would need to construct Python objects that would then be unpacked into Fortran-callable functions by the F2PY-generated module. Since the purpose of the programmer who is trying to call Fortran routines with Cython is to improve code performance, this is an obvious bottleneck.
I like the proposed approach, and I'm not sure at all that we need the Fortran scanner (unless Cython scans an INTERFACE block), because it's a lot of work. The proposed approach offers the programmer the ability to call Fortran from Cython without having to deal with all the ins and outs of C/Fortran integration. All I'd like to be able to do is to have some syntactical cues that I can use to tell Cython that I have a function in Fortran that takes some arguments and returns something, and have Cython handle the dirty work. I may be wrong, but that seems a lot less intensive than F2PY, and takes advantage of the power of Cython. Thanks. --v On Tue, Mar 24, 2009 at 10:48 AM, Gabriel Gellner <[email protected]>wrote: > > [X] No, that would bloat the language and/or the compiler/project too > > much, I'd prefer to see this in a standalone tool/plugin > > > Just my opinion, but f2py rocks at this, so it seems like a distraction to > me. > > Gabriel > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > -- Vic Kelson [email protected]
_______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
