DOCERR: Reference Manual Documents BZ Edit Descriptor Wrong

Last reviewed: December 11, 1995
Article ID: Q49430
The information in this article applies to:
  • Microsoft FORTRAN for MS-DOS and OS/2, versions 5.0, 5.1
  • Microsoft FORTRAN PowerStation for Windows, versions 1.0 and 1.0a
  • Microsoft FORTRAN PowerStation32 for Windows NT, version 1.0 and 4.0

In the Microsoft FORTRAN "Reference" manual for versions 5.0 and 5.1, the last paragraph of page 86, in the FORTRAN PowerStation32 for NT Programmer's Guide, page 116 (second paragraph), in the FORTRAN PowerStation 1.0 for Windows Programmer's Guide, on page 88 (second paragraph), and in the FORTRAN PowerStation 32, version 4.0 on-line docs, you will find the following statement:

   ... so the first thing the I/O system does is to pad the record 502
   on the right with two blanks. If BZ editing were in effect, those
   two blanks would be interpreted as zeros, and the record would be
   equal to 50200.

This statement is incorrect. The BZ edit descriptor is designed to replace any spaces in the input with zeros, provided the space is not a leading space.

Contrary to the statement in the documentation, the I/O system does not pad spaces to the right of the two; therefore, the BZ edit descriptor does not add zeros to the end of the number.

When BZ editing is in effect, if the user types 502 and presses ENTER, the variable read receives the value 502, not 50200. However, if the user enters 502 followed by two spaces and presses ENTER, the variable read receives the value 50200.


Additional reference words: 5.00 5.10 1.00 4.00
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: December 11, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.