Q61406: NOFLTIN.OBJ: Hex Numbers Not Allowed with INPUT, READ, or VAL
Article: Q61406 Product(s): See article Version(s): 7.00 7.10 | 7.00 7.10 Operating System(s): MS-DOS | OS/2 Keyword(s): ENDUSER | SR# S900409-55 | mspl13_basic Last Modified: 21-SEP-1990 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 "legal long integers," 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. This information applies to Microsoft BASIC Professional Development System (PDS) versions 7.00 and 7.10 for MS-DOS and MS OS/2. 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 "Redo from start" READ - returns "Syntax error in module <module name>" VAL - returns a value of 0
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.
Copyright Microsoft Corporation 1986-2002.