FIX: Nested $IF Statements With $ELSE Fail

 Last reviewed: September 16, 1997
Article ID: Q84164
5.10 1.00 1.00a | 5.10 | 1.00 4.00 
MS-DOS          | OS/2 | WINDOWS NT
kbtool kbfixlist kberrmsg

The information in this article applies to:

  • Microsoft FORTRAN for MS-DOS, version 5.1
  • Microsoft FORTRAN for OS/2, version 5.1
  • Microsoft FORTRAN PowerStation for MS-DOS, versions 1.0 and 1.0a
  • Microsoft FORTRAN PowerStation 32 for Windows NT, version 1.0

SYMPTOMS

Compiling code that contains nested $IF compiler conditions with $ELSE clauses fails to produce the expected result. The compiler issues error: 

   error F2830: END missing
This error is generated because all of the source code following the $ELSE condition fails to be compiled.

CAUSE

When there is a $ELSE following a $ENDIF and the outer $IF condition is met making the $ELSE condition false the compiler fails to parse for any metacommands following the $ELSE including the $ENDIF that terminates the outer $IF block.

RESOLUTION

Do not use nested $IF metacommands with $ELSE clauses.

STATUS

Microsoft has confirmed this to be a problem in the products listed above. This problem was corrected in Microsoft FORTRAN PowerStation 32, version 4.0.

MORE INFORMATION

The following code reproduces the problem:

Sample code

$define first 

      subroutine test
$if defined (first) $if defined (second) $endif $else $endif 
      return
      end

Additional reference words: 5.10 1.00 1.00a
KBCategory: kbtool kbbuglist kbfixlist kberrmsg
KBSubcategory: FLIss
Keywords : FLIss kbbuglist kberrmsg kbfixlist kbtool
Version : 5.10 1.00 1.00a | 5.10 | 1.00 4.
Platform : MS-DOS NT OS/2 WINDOWS
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.