BUG: Problems Passing Arguments to ENTRY Statement (73203)
The information in this article applies to:
- Microsoft FORTRAN compiler for OS/2 4.1
- Microsoft FORTRAN compiler for OS/2 5.0
- Microsoft FORTRAN compiler for OS/2 5.1
This article was previously published under Q73203 SYMPTOMS
Programs compiled with Microsoft FORTRAN versions 4.0, 4.01, 4.1, 5.0,
and 5.1 can generate a protection violation when run under OS/2, if a
program contains the following:
- An ENTRY statement to enter a SUBROUTINE or external FUNCTION
- A CALL to the SUBROUTINE or external FUNCTION
- An argument that is referenced in the ENTRY statement but not in
the SUBROUTINE or external FUNCTION statement, and is then used in
the ENTRY section of the SUBROUTINE or external FUNCTION.
According to the ANSI FORTRAN 77 standard, the order, number, type,
and names of the formal arguments in an ENTRY statement may be
different from the order, number, type, and names of the formal
arguments in the FUNCTION statement or SUBROUTINE statement and other
ENTRY statements in the same subroutine.
RESOLUTION
To avoid this problem, pass the argument to the SUBROUTINE or external
FUNCTION as well as to the ENTRY point.
STATUS
Microsoft has confirmed this to be a problem in FORTRAN versions 4.0,
4.01, 4.1, 5.0, and 5.1 for OS/2. We are researching this problem and will
post new information here as it becomes available.
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | KB73203 |
---|
|