BUG: F1001 Error If Undeclared Namelist Variable in Subroutine

Last reviewed: March 18, 1996
Article ID: Q148604
The information in this article applies to:
  • Microsoft Fortran PowerStation for Windows 95 and Windows NT, version 4.0

SYMPTOMS

Using an undeclared variable in a NAMELIST statement in an internal subroutine when the undeclared variable has the same name as one used in the superceding program unit in another NAMELIST statement may cause the following internal compiler error:

   fatal error F1001: INTERNAL COMPILER ERROR
   (compiler file '..\..\\P2\main.c', line 374)

   Please choose the Technical Support command on the Developer Studio
   Help menu, or open the Technical Support help file for more information

RESOLUTION

Explicitly declare all NAMELIST variables in your internal subroutines.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Sample Code to Illustrate Problem

C Compile options needed: none

      PROGRAM IOLIST
      INTEGER I
      NAMELIST /MAIN_LIST/ I
      I = 1
      CALL LOCAL()
      CONTAINS
        SUBROUTINE LOCAL()
C         INTEGER I       ! Uncommenting this line prevents the error
          NAMELIST /SUB_LIST/ I
          I = 2
        END SUBROUTINE LOCAL
      END PROGRAM IOLIST


Additional reference words: 4.00
KBCategory: kbprg kbbuglist
KBSubcategory: FORTLngIss


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: March 18, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.