Q35666: In QB.EXE, Improper FOR NEXT Control after NEXT Is Inserted
Article: Q35666
Product(s): See article
Version(s): 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | buglist4.00 buglist4.00b buglist4.50 B_BasicCom | mspl13_basic
Last Modified: 12-DEC-1989
In the QB.EXE editor, when a NEXT statement is inserted inside a
nested FOR NEXT loop after a "FOR WITHOUT NEXT" error has occurred,
loop control is incorrectly executed.
Microsoft has confirmed this to be a problem in Microsoft QuickBASIC
Versions 4.00, 4.00b, and 4.50, and in the QB.EXE that comes with the
Microsoft BASIC Compiler Versions 6.00 and 6.00b for MS-DOS and MS
OS/2 (buglist6.00, buglist6.00b). This problem was corrected in the
Microsoft BASIC PDS Version 7.00 (fixlist7.00).
To duplicate this problem, do the following:
1. Enter the following code in the QuickBASIC editor:
CLS
FOR k = 1 to 5
FOR l = 1 to 2
PRINT k
NEXT
Running this will give the FOR WITHOUT NEXT error.
2. Insert another NEXT statement after the "PRINT k" and run the
program again.
The output should be as follows:
1 1 2 2 3 3 4 4 5 5
However, it is as follows:
1 1 2 2
If the NEXT is inserted after the already existing NEXT, the
program runs correctly.
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.