Re: right sequence of included module files

On Sat, 26 Apr 2008 16:30:28 -0700 (PDT), jwm <jwmwalrus@xxxxxxxxx> wrote:

If I recall correctly, the *.mod and included files used to show up in
the external dependencies folder in Digital/Compaq Visual Fortran.
That feature seems to have been removed in IVF/VS2002, along with the
ability for the IDE to automatically add the included files as
external dependencies (i.e., if you want them listed in the solution
explorer in VS200x, they must be added manually and excluded from
build).

I had forgotten that CVF did that, but you are correct. Current versions of
Intel Visual Fortran will try to sort out include files when you add them to
the project, but it does so by file type (.fi for example) and not by looking
at INCLUDEs.
--
Steve Lionel
Developer Products Division
Intel Corporation
Nashua, NH

For email address, replace "invalid" with "com"

User communities for Intel Software Development Products
http://softwareforums.intel.com/
Intel Fortran Support
http://support.intel.com/support/performancetools/fortran
My Fortran blog
http://www.intel.com/software/drfortran
.

Relevant Pages

  • Re: Retrieving position of a dialog in (Compaq) Visual Fortran
    ... This would be a great question to ask in the Intel Visual Fortran user forum - ... Developer Products Division ... User communities for Intel Software Development Products ...
    (comp.lang.fortran)
  • Re: New Visual Fortran Product Survey
    ... I assume that MS authorized DEC to use the name, and that that authorization transferred to Compaq/HP and then to Intel when the compiler/components/rights were successively purchased by those companies. ... HP does own and retain the rights to DEC/Compaq Visual Fortran, and their disuse of it does not give anyone else a right to use it. ... I believe the wording which says the product is only for Windows X64 EM64T and AMD64, for which only a minority of the vendors mentioned above have a product. ... I would expect most of the above vendors to produce such a compiler for whatever architecture becomes predominant, ...
    (comp.lang.fortran)
  • Re: Intel 10.0 vs 9.1
    ... used by the compiler, those would not be in the old libraries. ... There is one particular link compatibility issue that involves module ... I would also suggest that if you have further questions about Intel ... Visual Fortran that you take advantage of our free technical support ...
    (comp.lang.fortran)
  • Re: problem with NEQNF
    ... Digital) Visual Fortran and had converted their project to Intel ... then is that the stack is incrementally corrupted on each call to FCN, ... calling convention back to the Intel default. ...
    (comp.lang.fortran)
  • Re: Which compiler (long)
    ... Visual Fortran has not "bounced around" as much as you think. ... working for Intel and bringing you, with the added muscle of additional Intel ... Intel Fortran compilers with exceptional performance and a large feature set. ... full support, ...
    (comp.lang.fortran)