Microsoft KB Archive/61406

= NOFLTIN.OBJ: Hex Numbers Not Allowed with INPUT, READ, or VAL =

Article ID: 61406

Article Last Modified on 10/20/2003

-

APPLIES TO


 * Microsoft BASIC Professional Development System 7.0
 * Microsoft BASIC Professional Development System 7.1

-



This article was previously published under Q61406



SUMMARY
When you LINK the stub file NOFLTIN.OBJ into a program compiled with the /O switch, or into a custom run-time module built with BUILDRTM.EXE, the numeric parsing code will be replaced with an integer-only version.

If you link with NOFLTIN.OBJ, all numbers used by INPUT, READ, and VAL must be within the range of legal long integers.

Although it seems that a number represented in hexadecimal should fall into the category of &quot;legal long integers,&quot; it does not. A program that INPUTs, READs, or uses the VAL function on a hexadecimally represented integer will either generate an error or return incorrect results. Hexadecimal number parsing is also eliminated with the NOFLTIN.OBJ stub file.



MORE INFORMATION
The following is an explanation of what happens when a program linked with the NOFLTIN.OBJ stub file uses either the INPUT, READ, or VAL commands on a hexadecimal number:

INPUT - returns a &quot;Redo from start&quot;

READ - returns &quot;Syntax error in module &quot;

VAL - returns a value of 0

Additional query words: BasicCom

Keywords: KB61406

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.