Using the DF or FL32 Command Line

You can use either the DF or FL32 commands to compile (and link) your application. The main difference between the DF and FL32 commands is the defaults set for certain command-line options:

• FL32 requests no optimization (/Od). See /[no]optimize.
• FL32 requests checking of arguments passed to and results from the math library (/math_library:check or /Od). See /[no]math_library.
• FL32 provides minimal debug information (/debug:minimal or /Zd). See /[no]debug.
• FL32 requests full Microsoft Fortran PowerStation compatibility (/fpscomp:all). See /[no]fpscomp.
• FL32 disallows alternative PARAMETER syntax (/noaltparam). See /[no]altparam.
• FL32 requests record length units for unformatted files to be in bytes (/assume:byterecl). See /assume.
• FL32 requests warnings for mismatched arguments (/warn:argument_checking). See /[no]warn.
• FL32 compiles each source unit individually and retains intermediate files that would otherwise be deleted (/keep). This prevents interprocedure optimizations at higher optimization levels. See /keep.
• FL32 does not display an informational message related to compiling multiple files individually. See /warn:fileopts.
• FL32 requests no inlining (/inline:none). See /[no]inline.
• FL32 places module files in the same directory as the object files. See /module:path.

The DF and FL32 commands both:

• Recognize the same set of command-line options. For example, the following commands are supported:

    DF   /Odx test2.for
    FL32 /Odx test2.for
  

  Both DF and FL32 command lines allow most Microsoft Fortran PowerStation style options (such as /Ox) and all Visual Fortran options (such as /optimize:4). For a detailed list of equivalent Microsoft Fortran PowerStation style compiler options and Visual Fortran compiler options, see Equivalent Visual Fortran Compiler Options.

• Activate the same compiler, the Compaq Fortran compiler.

  For new programs and most existing applications, use the Compaq Fortran compiler (default). The Compaq Fortran compiler and language used by Visual Fortran provides a superset of the Fortran 95 standard with extensions for compatibility with previous versions of Compaq Fortran (DIGITAL Fortran, DEC Fortran), VAX FORTRAN, and Microsoft Fortran PowerStation Version 4.

• Pass options specified after /LINK to the LINK command.

  The LINK command options after /link are passed directly to the Linker. These options are described in Linker Options.

• Allow the use of indirect command files.

  For example, assume the file text.txt contains the following:

   /pdbfile:testout.pdb /exe:testout.exe /debug:full /optimize:0 test.f90 rest.f90
  

  Either of the following (DF or FL32) commands executes the contents of file text.txt as an indirect command file to create a debugging version of the executable program and its associated PDB file:

    DF   @test.txt
  
    FL32 @test.txt
  

To request Microsoft Fortran PowerStation V4 compatibility, specify the /[no]fpscomp option.

For information about using the DF command, see Using the Compiler and Linker from the Command Line.