BUG: Dependencies Not Scanned If Include Statement Is Labeled

Last reviewed: July 13, 1995
Article ID: Q106732
The information in this article applies to:
  • Microsoft FORTRAN PowerStation for MS-DOS, version 1.0 and 1.0a
  • Microsoft FORTRAN PowerStation 32 version 1.0

SYMPTOMS

Dependencies are not scanned for include files containing statement labels (for example, line numbers). Also, the included file doesn't appear in the Visual Workbench file list.

RESOLUTION

Do not use statement labels with include statements.

STATUS

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

MORE INFORMATION

To demonstrate this problem, follow these steps:

  1. In the Visual Workbench, create a project containing the sample program; it will scan dependencies for "FLIB.FI" but not for "FLIB.FD."

  2. Display the File List (click the icon below the File menu). FLIB.FI will be listed but not FLIB.FD.

NOTE: If the include files are not being modified, and if the project is large and is modified often, placing statement labels on include statements will speed up the process of scanning dependencies.

Sample Code

      include 'flib.fi'
  2   include 'flib.fd'
      print *, 'Hello'
      end


Additional reference words: 1.00 slow scan disable
KBCategory: kbtool kbbuglist
KBSubcategory: VWBIss


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: July 13, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.