<<
key files
kind type parameter
INTEGER declarations
LOGICAL declarations
language extensions
and portability
messages for Intel(R) Fortran
language standards
and portability
LD_LIBRARY_PATH environment variable
length
options controlling size of COMPLEX declarations
options controlling size of INTEGER or LOGICAL declarations
options controlling size of REAL declarations
LIB environment variable
LIBIFCOREMT.LIB
libraries
creating shared
default
for the compiler
IFPORT portability module
math
static
libraries used when linking
library directory paths when linking
library exception handler
overriding
library routines
how to use
license file
specifying the location of
limitations of mixed-language programming
limits
Intel(R) Visual Fortran compiler
line length
option extending fixed-format source
link map file
generating
linker
Microsoft*
option to prevent running
request threaded run-time library
using from the command line
viewing libraries used
linker diagnostic messages
linker error conditions
linker library directory paths
linking
against additional libraries
linker option specifying how to display
object files
option suppressing
list-directed I/O
list-drected I/O statements
little endian storage
local program analysis
locations
specifying alternative
logical data
mixed-language programming
logical data representation
logical data type
converting nonnative data
declaring
differences with nonnative formats
mixed-language programming
ranges
representation
logical devices
logical records
logical unit number
logical units
assigning files to
lowercase names
case-sensitivity
Adjusting Naming Conventions in Mixed-Language Programming
Naming Conventions for Fortran, C, Visual C++, Visual Basic, and MASM
Reconciling the Case of Names
LST files
macros
make command
makefiles
command-line syntax
MAP
files
MASM
math libraries
memory models
messages
display of run-time
language dialects and standards checking
limiting the number of compile-time
meaning of severity to run-time system
run-time error
run-time format
methods of specifying the data format
Microsoft
debugger
linker
Microsoft Fortran PowerStation
compatibility with
compatible file types
Microsoft Visual Studio* IDE
using
mixed-language programming
adjusting case of names
adjusting naming conventions in
Adjusting Naming Conventions in Mixed-Language Programming
Naming Conventions for Fortran, C/C++, Visual Basic, MASM
allocatable arrays in
array descriptor format
array pointers in
arrays in
calling conventions in
character strings in
exchanging and accessing data in
handling data types in
integer pointers in
limitations
naming conventions
numeric data types in
overview of issues
passing arguments in
return values
Handling Character Strings
Handling Numeric, Complex, and Logical Data Types
summary of issues
user-defined types in
using common external data in
using modules in
mixed-language programs
ATTRIBUTES Properties and Calling Conventions
Calling C Procedures from a Fortran Program
Fortran Module Names and ATTRIBUTES
Naming Conventions for Fortran, C, Visual C++, Visual Basic, and MASM
Protoyping a Procedure in Fortran
Visual C/C++ and Visual Basic Naming Conventions
compiling and linking
debugging
mixed-language projects
programming with
mixed language programming
calling subprograms
module naming conventions
modules
advantages of
IFPORT
use in mixed-language programming
multibyte characters
multithread applications
compiling and linking
See Also threads
multithreaded programs
debugging
namelist I/O
namelist I/O statements
naming conventions
mixed-language programming
native and nonnative numeric formats
native numeric format
nmake command
NODECLARE
equivalent compiler option for
NOFREEFORM
equivalent compiler option for
nonadvancing i/o
nonadvancing record I/O
nonnative data
porting
nonnative numeric format
NOOPTIMIZE
equivalent compiler option for
NOSTRICT
equivalent compiler option for
notation conventions
numeric data types
mixed-language programming
numeric format
specifying with /convert
specifying with OPEN(CONVERT=)
specifying with OPTIONS statement
numeric values and conversion
portability routines for
OBJ files
OBJCOMMENT
equivalent compiler option for
object file
linking
OPEN
CONVERT specifier
OPEN Statement CONVERT Method
Supported Native and Nonnative Numeric Formats
defaults for converting nonnative data
example
example of ERR specifier
example of FILE specifier
example of IOSTAT specifier
RECL specifier
option to specify units
units for unformatted files
OPEN statement
Opening Files: OPEN Statement
Specifying the Initial Record Position
User-Supplied OPEN Procedures: USEROPEN Specifier
opening files
OPEN statement
OpenMP analysis
operating system
portability considerations
optimization
compiling and linking for
OPTIMIZE
equivalent compiler option for
option mapping tool
OPTIONS
compiler
precedence using CONVERT
specifying unformatted file floating-point format
output files
producing
output window
overview
configuration files
IFPORT portability module
LIBIFPORT.LIB
of compiler options
of debugging multithreaded programs
portability library
response files
overview of Building Applications
PACK
equivalent compiler option for
padding for blanks
PARAMETER
alternative syntax for
PATH environment variable
pathnames
specifying default
portability considerations
and data representation
and the operating system
data transportability
overview
recommendations
using IFPORT portability module
portability library
overview
portability routines
recommendations
post-installation troubleshooting
preconnected units
preprocessor
FPP
preprocessor symbols
predefined
procedure names
procedures
interface blocks for mixed-language programming
mixed-language programming
process control
portability routines for
proforder.exe file
program termination
values returned
programming practices
programs
advantages of internal procedures
advantages of modules
choosing development environment
debugging multithread
Fortran executables
mixed-language issues in
multithread
structuring
values returned at termination of
projects
errors during build
prototyping procedures
>>