Re: bye bye CVF

Ken Plotkin wrote: 
On Thu, 09 Jun 2005 09:32:37 -0400, Steve Lionel
<Steve.Lionel@xxxxxxxxxxxxxxxxx> wrote:

[snip]

So now we have a product that comes from essentially the entire CVF
development team, based on CVF sources (DVF was not based on PowerStation),
and there are again some who seem to view the transition as some sort of
personal betrayal.  I don't understand it.


[snip]

Some of us just hate change.  Hope I'm not regarded as one of those
who spewed insults or felt betrayed, but I do subscribe to some
Luddite attitudes.  At least as far as change goes.

Eventually, my colleagues and I will change compilers.  But I expect
that to be either when F2003 compilers are out and stable, or when
we've migrated to 64 bit processors.  That IVF really is CVF is a
really big plus in favor of IVF when the time comes.

I'm curious about one thing.  If IVF is now based on CVF, what was it
based on when first released, i.e. before Intel acquired that part of
Compaq, or just after, when the proposed migration was floated?

Ken Plotkin

But some seem to have missed the point. DVF/CVF was more than just the compiler. It was a complete integrated development environment. 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. However, it doesn't yet warrant being called "visual" until it is a complete integrated product and not requiring the purchase of separate products for much of its functionality. I even have no problem with them selling the product at a lower price in the present fashion. If they offered a complete product, I'd buy it instead, almost regardless of price.

--

Gary Scott
mailto:garyscott@xxxxxxx

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

Why are there two?  God only knows.


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: Compaq Visual Fortran discontinued: upgrade to Intel Visual Fortran?
    ... >> Thank you very much, everybody, for your responses so far. ... >> Is the integrated editor/debugger environment of IVF ... > w/ the compiler as was done w/ CVF. ... the compiler won't even run from the command ...
    (comp.lang.fortran)
  • Re: On the future of Compaq Visual Fortran !
    ... | finally abandoned CVF altogether. ... Intel has made a tactical ... That was one option -- the other was to make a better compiler than ... 48 MB under IVF. ...
    (comp.lang.fortran)
  • Intel nonVisual fortran
    ... > development team, based on CVF sources, ... pleased that the compiler is now derived from DVF/CVF... ... Can Intel sales spinners ...
    (comp.lang.fortran)
  • Interaction between CVF and IVF?
    ... I'm running into a problem with CVF that never occurred before and I'm ... the compiler only flags these ... it might be some kind of interaction between the CVF and IVF ...
    (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)
Loading