DOCERR: NODATA and pwords Parameters Switched in EXPORT Docs

 Last reviewed: July 17, 1997
Article ID: Q61605
5.01.21 5.02 5.03 5.05 5.10 | 5.01.21 5.02 5.03 5.05 5.10 
MS-DOS                      | OS/2
kbtool kbdocerr

The information in this article applies to:

  • Microsoft LINK for MS-DOS, versions 5.01.21, 5.02, 5.03 5.05, and 5.10
  • Microsoft LINK for MS-DOS, versions 5.01.21, 5.02, 5.03 5.05, and 5.10

SUMMARY

The EXPORT statement used in module definition (.DEF) files is incorrectly documented in several places with the last two parameters reversed. The "pwords" parameter should be the last parameter, but it is listed second from the end. The "NODATA" parameter is listed last, but should be second from the end. The correct EXPORT statement syntax is as follows: 

   entryname [=internalname] [@ord[RESIDENTNAME]] [NODATA] [pwords]
Note that the "pwords" parameter is listed as "iopl-parmwords" in some of the documentation.

MORE INFORMATION

The documentation with the incorrect EXPORT statement syntax with reversed parameters is as follows:

- The C versions 6.0 and 6.0a online help for LINK under the EXPORT 

  statement syntax
- On page 334 of "The Microsoft CodeView and Utilities User's 
  Guide" for version 2.3 in Section 19.9, "The EXPORTS
  Statement" (shipped with FORTRAN 5.0 and BASIC PDS 7.0)
- On page Update-52 of "The Microsoft CodeView and Utilities 
  Update" for version 2.2 in Section 7.8, "The EXPORTS
  Statement" (shipped with C 5.1, MASM 5.1, and Pascal 4.0)
LINK version 5.13 (shipped with MASM 6.0) was corrected.

Additional reference words: 5.01.21 5.03 5.03 5.05 5.10 docerr
KBCategory: kbtool kbdocerr
KBSubcategory: LinkIss
Keywords : kb16bitonly

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 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.