Re: Compaq Visual Fortran

Terence wrote:

The person who knows the answers to the problem of re-installing an
udgraded CVF compiler is of course, the man who worked and advised on
it; Steve Lionel.

The problems is: Steve moved with the compiler, to Intel and therefore
has tp support Intel's replacement version by NOT telling you how to
do this in a public Forum.

I don't think theres any prohibition. I've seen him explain such things before. It's probably includes a bit of relationship to the fact that it's an obsolete product and he gets tired of answering the same old questions for an obsolete product. The intel forum is still a good place to ask these questions. After all, many if not most clinging to CVF will eventually transition to IVF at some point. So there is still incentive.


You could always, of course try writing to any of the previous support
group addresses and/or personnel.

I use CVF 6.6c myself, on top of an early MS Visual Studio.
It's a bit finicky to get all the option settings right, but I never
had problems with results of this compiler, other than not ever being
able to get RS232C ports to work the way I was accustomed.


--

Gary Scott
mailto:garylscott@sbcglobal dot net

Fortran Library: http://www.fortranlib.com

Support the Original G95 Project: http://www.g95.org
-OR-
Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html

If you want to do the impossible, don't hire an expert because he knows it can't be done.

-- Henry Ford
.

Relevant Pages

  • Re: Fortran 90 modules suck for portability- why use them?
    ... As far as ensuring that libraries are produced to be compatible with a foreign compiler, again, it's nice to be able to specify -interface:cvf6 or something as a composite of one or more sub-options. ... Microsoft withdrew compatibility with portions of that interface when they introduced 64-bit support, after which HP withdrew support for CVF. ...
    (comp.lang.fortran)
  • Re: Fortran 90 modules suck for portability- why use them?
    ... As far as ensuring that libraries are produced to be compatible with a foreign compiler, again, it's nice to be able to specify -interface:cvf6 or something as a composite of one or more sub-options. ... Microsoft withdrew compatibility with portions of that interface when they introduced 64-bit support, after which HP withdrew support for CVF. ...
    (comp.lang.fortran)
  • Re: IVF is a wonderful compiler (was IVF continues to disappoint(relatively))
    ... "But, had the CVF line continued, I'm certain that most if not all of those compiler bugs would have been fixed as well in that line. ... Support the Original G95 Project: http://www.g95.org ... Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html ...
    (comp.lang.fortran)
  • Re: CVF to Intel USE statements
    ... It's good to hear that the Premier Support login will be improved. ... The developer used CVF. ... converting all source modules to Fortran 90 syntax; ... Most likely this research group user will lease the Intel Compiler ...
    (comp.lang.fortran)
  • Re: bye bye CVF
    ... development team, based on CVF sources, and there are again some who seem to view the transition as some sort of personal betrayal. ... really big plus in favor of IVF when the time comes. ... I'm pleased as punch that the compiler is now derived from DVF/CVF and that the ~DEC/Compaq compiler team is intact and supporting it. ...
    (comp.lang.fortran)
Loading