>>Somewhere around here I think I saw something like
>>

local cVariable as string = "some text"

>>and I think I saw this as a welcome change - i.e. a chance to declare and initialize a variable in a single command. Just tried
>>

local i as integer = 0

>>and it compiled fine, didn't error out in runtime, but the value of i was .f., so it seems to ignore the assigned value. Help, of course, doesn't mention this, but it also has another error where it says it accepts ARRAY keyword (which it doesn't anymore, had to delete a bunch of these yesterday, it decides a variable is an array when it sees it with dimensions - much simpler, IMO).
>>
>>OK, it doesn't work as I thought, but then what's the purpose of this? Is it just another "parser doesn't look behind this point" issue, as in the EndIf, EndScan and such commands (where you can put any text after the space after the command and it's treated as a comment), or does it have any use in intellisense, or what?
>
>Yep, another bug in the parser. It should generate 'Syntax error' message.

Too bad. It would be nice if it worked this way.