DOCERR: $PACK: Metacommand Syntax Documented Incorrectly

 Last reviewed: July 18, 1995
Article ID: Q49450
The information in this article applies to:
  • Microsoft FORTRAN for MS-DOS and OS/2, versions 5.0 and 5.1

SYMPTOMS

An attempt to compile an application fails and the compiler generates the following message: 

   F2030: unrecognized metacommand

CAUSE

The source code specifies the $PACK: metacommand without its required trailing colon (:) character.

RESOLUTION

Modify the source code to specify the colon character.

This error has been corrected in the FORTRAN PowerStation Language Help.

MORE INFORMATION

Page 305 of the Microsoft FORTRAN "Reference" manual for version 5.0 documents the $PACK: metacommand incorrectly three times. First, the following syntax statement is incorrect. 

   $PACK[:{1|2|3}]
This statement indicates that the colon is an optional character. The correct syntax statement is as follows: 

   $PACK:[{1|2|3}]
Second, the second-to-last paragraph on the page is also incorrect. It includes the following statement: 

   If $PACK is specified (no colon or number), packing reverts to
   whatever mode was specified in the command-line /Zp option.
Because the $PACK: metacommand must include a colon, this statement should be corrected to read as follows: 

   If $PACK: is specified (without a number), packing reverts to
   whatever mode was specified in the command-line /Zp option.
Third, the example of using $PACK: is incorrect. On the first line of the example, add the colon character to the $PACK: metacommand.

Additional reference words: 5.00 5.10
KBCategory: kbprg kbdocerr
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: July 18, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.