A to Z Reference

This section contains the following:

• Language Summary Tables

  This section organizes the functions, subroutines, and statements available in Intel® Visual Fortran by the operations they perform. You can use the tables to locate a particular routine for a particular task.

• The descriptions of all Intel Visual Fortran statements, intrinsics, directives, and module library routines, which are listed in alphabetical order.

  In the description of routines, pointers and handles are INTEGER(4) on IA-32 architecture and INTEGER(8) on Intel® 64 and IA-64 architectures.

The Fortran compiler understands statements and intrinsic functions in your program without any additional information, such as that provided in modules.

However, modules must be included in programs that contain the following routines:

• Quickwin routines and graphics routines (W*32, W*64)
  
  These routines require a USE IFQWIN statement to include the Intel Visual Fortran library and graphics modules.
  
  
• Portability routines and serial port I/O routines
  
  These routines require a USE IFPORT statement to access the portability library. The serial port I/O routines are only available on Windows* systems.
  
  
• NLS routines (W*32, W*64)
  
  These routines require a USE IFNLS statement to access the NLS library.
  
  
• POSIX* routines
  
  These routines require a USE IFPOSIX statement to access the POSIX library.
  
  
• Dialog routines (W*32, W*64)
  
  These routines require a USE IFLOGM statement to access the dialog library.
  
  
• Component Object Module (COM) routines (W*32, W*64)
  
  These routines require a USE IFCOM statement to access the COM library.
  
  
• Automation server routines (W*32, W*64)
  
  These routines require a USE IFAUTO statement to access the AUTO library.
  
  
• Miscellaneous Run-Time Routines
  
  Most of these routines require a USE IFCORE statement to obtain the proper interfaces.

Whenever required, these USE module statements are prominent in the A to Z Reference.

In addition to the appropriate USE statement, for some routines you must specify the types of libraries to be used when linking.

See Also

• Building Applications:
  
Understanding Errors During the Build Process
• For information on conventions used in this document, see How To Use This Document