Re: Structure of large link libraries in f95



Paul Van Delst wrote:
Charles Russell wrote:

Why would you have to recompile everything? Can't you just recompile the routines you're "monkeying with" and replace them in your library(ies)?

I think you have to recompile a whole module if you change any component
of it. Since my "user interface" is to edit the source, I want fast turnaround.

But, if you changed the interface you would have to change the corresponding interface block in your "interface block module(s)".

But why do you want to cast your existing, working libraries, in fortran95 anyway? I use the f77 blas/lapack (and others) libraries in my f95 code and when I use various routines from them, I declare them EXTERNAL and link in the required library -- which was compiled once and pretty much forgotten about

But then you get no type checking. That is OK if you can fall back on ftnchek to find your mistakes, but ftnchek won't work with f95 code. I make lots of mistakes and rely on a highly protected programming environment to find them quickly. Some people, I have been told, get things right the first time.

Old and comfortable do not necessarily translate into good for your feet. :o)

The risk of blisters with new shoes is hard to predict.

It sounds like you've got everything working the way you want it, with a system set up for quick and easy modification. Why even bother with f95 constructs with your existing library setup? "If it ain't broke...." type of thing.

When the rest of my department switched from fortran to C around 1990, I
figured I'd better prepare a bridge to C. When Lahey later dropped support for its fine f77 compiler, I figured I'd better prepare a bridge to f90. So far I haven't had to cross either bridge, but I still consider it prudent to reconnoitre the route and get some idea of what lies on the other side of the bridge.
.



Relevant Pages

  • Re: Structure of large link libraries in f95
    ... Can't you just recompile the routines you're "monkeying with" and replace them in your library? ... corresponding interface block in your "interface block module". ... I use the f77 blas/lapack libraries in my f95 code and when I use various routines from them, I declare them EXTERNAL and link in the required library -- which was compiled once and pretty much forgotten about ... When Lahey later dropped support for its fine f77 compiler, I figured I'd better prepare a bridge to f90. ...
    (comp.lang.fortran)
  • Re: Stack frames
    ... _MOST_ routines often don't need to be (so, ... registers and just stuff your parameters into those registers...if the ... This type of situation - especially with modern OS designs and "libraries" ... assemblers don't have or can't match due to the way they operate_...one of ...
    (alt.lang.asm)
  • Re: FASMLIB 0.5.0 is out
    ... He's talking about "cut and paste" programming techniques, ... keeps copies of his library routines in a separate file and copies ... Absence of libraries makes development time too long for ... then it's okay to use that library routine, as his assembler *can* ...
    (alt.lang.asm)
  • Re: Comics, Was Re: Volume 3 Available Monday
    ... >>> unexpectedly sank a foot or so shortly after it opened. ... >> I do not know about the university libraries, however, the building in ... >bridge that was supposed to extend from one part of the library, ...
    (rec.arts.sf.tv.babylon5.moderated)
  • Re: Comics, Was Re: Volume 3 Available Monday
    ... >> I heard a story once, the truth of which I've never been able to verify - ... > I do not know about the university libraries, however, the building in ... > work has two interesting design flaws: ... bridge that was supposed to extend from one part of the library, ...
    (rec.arts.sf.tv.babylon5.moderated)