Bug Reports

[v3cz0r]

Code:

NEXT x, y

Yeah, only single identifiers are accepted (as shown at docs/keywords.txt, will have to be documented).

Code:

LINE INPUT sn$: sn$ = LCASE$(sn$)

I'm checking just for newline, forgot about colon, will add that.

Code:

LINE INPUT ">"; sn$: sn$ = LCASE$(sn$)

Didn't know you could use console input w/o a msg, will correct that too.

Code:

CLOSE

That neither, heh.. i should read QB online docs better next time.. there's RESET, will just remap that CLOSE to that instead.

Code:

junk at the end of line, first unrecognized character is `-'

Yeah, it was corrected on the last version, 0.04b. "-" is a valid character on file names but isn't on symbols, and as every QB module can be a main module, i can't use a default name for the entry point or a name clash would happen, it's "guessed" from source's name.

Thx for reporting, will fix asap.

[Z!re]

Funny thing:

Code:

dim a as integer
a = 533

print "test" a

Output:
test
533


Look carefully at the print, it should crash.

[Jofers]

That's not a bug, it's a feature!

...

...

*looks shifty-eyed*

[Z!re]

Code:

'$include: "includefile.bi"
'$include: "includefile.bi

Both valid entries, soo... uhm.. whats up?


Should I add this to the feuture list or what

[Z!re]

Code:

Open "universe:\space\tada\woho::" for append as #1
close #1

Code:

open "c:\windows\windows\windows\blarg\does not exist\really, it doesent\i swear\for reall, just give it up\a file.txt" for append as #1
close #1

Shouldnt open return an error?, or something?..

[Jofers]

The second one's a perfectly valid filename.

first one isn't, but aren't these all matters for the runtime?

[v3cz0r]

Compile with the -e option (-e: add error checking).

All quirks fixed, including the NEXT with multiple identifiers (that i hate, btw). Will upload the new version tonight, but modifications are on CVS already, if anyone want to recompile the compiler: http://cvs.sourceforge.net/viewcvs.py/fbc (CVS when browsed by web takes some minutes to be updated).

Changelog:

Code:

[added] NEXT with multiple identifiers (NEXT a, b, ...), as many old sources seem to have that (v1ctor)
[fixed] PRINT and WRITE stmts were accepting expressions separated by white-spaces (BC also allows that) (v1c)
[fixed] quirks with LINE INPUT and INPUT for console, message is optional (try parsing that using a LR..) (v1c)
[fixed] and another one with CLOSE, file number is also optional and that way it works as RESET (v1c)

[Z!re]

My point is jofers.. that folder doesent exist, nor will it be created by open.

[na_th_an]

I've noticed that CSRLIN is not working. This code:

Code:

CLS
FOR i% = 1 TO 10
   PRINT CSRLIN
NEXT i%

Returns always 0, when it should return the current line where the cursor is. That is: from 1 to 10.

FB 0.04b.

[na_th_an]

And LINE INPUT should not display a "?", I almost forgot