> First step for kaplibs is to break it up into kpg, fts, irq etc and move
> them up a level in the directory structure. A kaplibs directory could be
Exactly. They should also have separate SUNs (I note an earlier KAPPA
offshoot, shl, doesn't yet).
> > astronomers to use the facilities to write their own tools. Should we
> > be converting old Fortran to C?
>
> No new fortran code should be written because it is completely impossible
> to multi-thread it (I've been saying this for ages).
It's often easier to adapt existing code than start from scratch.
You didn't answer my question. Whether or not the new stuff is in
Fortran isn't going to make a lot of difference to address the
multi-threading problem, if the bulk of the applications code remains
in Fortran. So along those lines I was wondering what can be done to
the legacy code.
Malcolm
|