Recent changes to bugs

Line number references in compound statements

2007-04-17T21:17:00Z

Line numbers do not work correctly when in compound statements if a RENUMBER is issued.

For example,

100 GOTO 800 : GOTO 800 : GOTO 800

This (admittedly ridiculous) example will not RENUMBER correctly. The problem is that the array of token positions for line numbers is not offset for the token position in the entire statement; instead it is for the relative position within each sub-statement. So the above line has three line number token positions, but they are [1, 1, 1], rather than the more correct [1, 4, 7].

This will require the compound statement handler in the Statement compile() method to copy sub-statement token position vectors to the parent statement and calculate offsets along the way, mindful of the recursive nature of the compile of each substatement.

Need to support multiple statements on a line

2007-03-05T01:45:05Z

GWBasic and others allow multiple statements on a line, with a separator (usually ":" or "\" characters). These multiple statements are semantically a single statement, so you can have:

100 IF X = 3 THEN PRINT "FINISHED!" : GOTO 300

If the condition is true, both the PRINT and GOTO statements are executed. This will require a couple of things in JBasic.

1. Statement compilation will have to be chained when there is a ":" as the next token after successful compilation; the chaining operation will locate the next verb and (recursively? serially?) invoke the next verb. The generated statements will probably be STMT 0-type statements in the same bytecode object for the first containing Statement.

2. The line number marker in each statement used to track tokenized line numbers for RENUMBER support will have to become a list, because it will be possible to have more than one line number in a given statement. This is probably already true with IF..THEN GOTO...ELSE GOTO.. statements anyway.

Recursion doesn't work in functions

2006-07-13T17:26:02Z

A FACT() function written to calculate a factorial
recursively won't work - the passing/management of
scope for the nested call frames does not appear to
work properly at all.

FUNCTION FACT( V )
// Version: 1.0
// Date: Wed Jun 21 14:16:00 EDT 2006
// Author: cole
IF V <= 2 THEN RETURN V
LET X < LOCAL > = FACT( V - 1 )
LET Y < LOCAL > = V * X
RETURN Y

This gets into an infinite loop with FACT(3).

FILE status is overloaded with non-localizable substitutions

2006-01-22T20:30:42Z

The Status.FILE error state is overloaded. It is a generalized prefix that
accepts a substitution string, which is usually where the real error is
defined.

The Status.FILE errors should be broken down into a set of errors for the
various actual file conditions, such as

FILESYNTAX
FILENOTFOUND
FILEREADERR
FILEWRITEERR

or something similar.