And I am confused because it sounds like you are saying that fortran (77) subs take subroutine (the fortran kind) as arguments. I actually recommend a shell script in this case. Once you have that, you can easily create a simple Perl (or even shell) front end that creates whatever interface you want around it. If the former, then I suggest creating an interactive fortran program that take in all arguments via STDIN (interactively, though). Thanks.Īre you trying to create a Perl script UI to an executable, or are you planning on using a fortran library as part of a Perl program? I think this is going to be a good exercise for this particular reader. I don't (quickly/easily) see that evapol is in the python package. Since someone in the python community has Dierckx's code working in python, I thought I would give it a try in perl. I've played with a lot of FORTRAN and perl over the years, but never together. (I'll leave it as anĮxercise for the reader to figure out how this all results in the final It is being called from within the Fortran code, and isĮxpected to return some value computed by Perl. The wrapper is responsible forĬalling the real Perl routine (via call_sv) and handling itsĪrguments (see perlcall for what all those macros areĭoing). Reference to the passed in user-defined Perl routine, and thenĬalls myfunc, which in turn calls the actual Fortranįunction myfunc_ (note the underscore, as automaticallyĪppended by g77), passing it a pointer to the callback wrapperįunction userfunc_wrapper. So what's happening in detail? P2f2p::myfunc isĬalling XS_P2f2p_myfunc under the hood, which is the XS wrapperįunction as expanded by xsubpp.
0 kommentar(er)
