Neil Carlson writes:
> The user callable routines are F77,
> but down a couple of layers I've got F90 module procedures....
> this library has been F77 (and the API still is) I need
> to be able to have it link using the familiar F77 compiler;
> I can't assume that everyone using the library has the F90
> compiler.
You don't quite explicitly say which f90 compiler you are using,
but from context I'd guess it was Sun's. The answers do vary
for this kind of question.
> 3) Incorporating libf90.a into our library. This should
> work, but is it legal?
You'd have to ask Sun (or whomever) about that. In a simillar
predicament using NAG f90, I got NAG to explicitly sell me a license
for unlimitted redistribution of their libf90.a in conjunction with my
code. So such things are certainly possible. Whether Sun would agree
to such a thing or not I couldn't say; I'd ask them. Some of my users
were using a C API on top of f90 innards, but the issues were pretty
much the same as yours.
--
Richard Maine
[log in to unmask]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|