Re: Intel nonVisual fortran

Well, Lahey has an agreement with MS, where you get the full VS when you buy
the compiler. I am not using Lahey anymore. They have started to become
license control freaks with online activation from v7.0 on, so now I am
using IVF. I really don't get the point. What is the difference between
buying VS separate and getting it from Intel with the Fortran compiler? I
like the Intel compiler and its integration in VS very much. For me it
simlified significantly the interfacing between C and Fortran, since all the
files can be arranged in one project. This was far more complicated in Lahey
5.7.

Haje


"Jan Vorbrüggen" <jvorbrueggen-not@xxxxxxxxxxx> wrote in message
news:3hvd1mFj65jqU1@xxxxxxxxxxxxxxxxx
>> Gary Scott noted:
>> "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 that the compiler is now derived from DVF/CVF... 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..."
>
> All nice and well - but if even Intel cannot coerce Microsoft to allow
> them
> to continue selling MSVS as part of their product, who can? I believe that
> even if you include the usual price for the minimally required components,
> IVF costs less than what DVF cost at the time.
>
> Jan


.

Relevant Pages

  • Re: Compaq Visual Fortran discontinued: upgrade to Intel Visual Fortran?
    ... I don't have a problem if Intel wants to offer as an option, an incomplete product such as their existing one. ... Just at least give me an option of a semi-complete one without requirement to buy a competitor's compiler and install them separately, ... IMHO, it would have been laudible if Lahey and Salford had been able to offer native code debugging and profiling, and had achieved as much success with their Windows products of the last 4 years as they did prior to .NET. ...
    (comp.lang.fortran)
  • Re: ambiguous INTREFACE
    ... but that constraint has nothing to do with it. ... The code here doesn't "specify a procedure that is specified ... I am implying nothing about Lahey. ... I also run code through NAG's compiler when I'm trying to decipher ...
    (comp.lang.fortran)
  • Re: Lahey/Fujitsu Fortran v7.1 released
    ... In the last year or so I've submitted 3 bugs to Lahey and they ... a bug involving a Lahey compiler than one involving the Intel Compiler. ...
    (comp.lang.fortran)
  • Re: Tom Laheys Fortran experiences
    ... > Tom Lahey is indeed a gifted teacher/leader in the field. ... > I was disappointd though to find out that Lahey Fortran is offering ... And the PathScale compiler is ... > XPL Compiler-Compiler by McKeeman, Horning and Wortman, ...
    (comp.lang.fortran)
  • Re: Which compiler (long)
    ... The only thing I dislike about the Lahey ... compiler is the runtime option thingo - but that's just my personal preference. ... Same for the linux version. ... price either - that's just the regular price. ...
    (comp.lang.fortran)