Dim At Issue? (1.15.0-beta4)

[Ljg701]

Hello Boriel,

The following array initiation code I don't think is initiating the array data at the correct address. In the example below, the peek returns a value of 255 rather than 1, also @test doesn't return a value of $c000  (Version  1.15.0-beta4 + NextBuild)

Code:

'!ORG=24576
'!OPT=4

dim test(0 to 3) as ubyte => {1,2,3,4} at $C000

'this should return 1
print at 0,0;peek($c000)

do
loop until inkey$<>""

[boriel]

Hello Boriel,

The following array initiation code I don't think is initiating the array data at the correct address. In the example below, the peek returns a value of 255 rather than 1, also @test doesn't return a value of $c000  (Version  1.15.0-beta4 + NextBuild)

Code:

'!ORG=24576
'!OPT=4

dim test(0 to 3) as ubyte => {1,2,3,4} at $C000

'this should return 1
print at 0,0;peek($c000)

do
loop until inkey$<>""

This is a bug in the sense that the compiler should report a syntax error.

It's not allowed to initialize an array with DIM AT (i.e. what if you initialize it into a ROM address?).
Allocation at a given memory address is not allowed (unless you declare asm code with ORG, which is NOT recommended).
Declaring things at given locations will be done outside the compiler (with a linker, and config files, and compiling to .obj, etc).

It's an effort that will take time, be patient, since this is required also for pagination, and interruptions.
Implementing things like this would make the compiler very architecture-dependent, and I want to move to a multi-architecture scheme.

[Ljg701]

Hello Boriel,

The following array initiation code I don't think is initiating the array data at the correct address. In the example below, the peek returns a value of 255 rather than 1, also @test doesn't return a value of $c000  (Version  1.15.0-beta4 + NextBuild)

Code:

'!ORG=24576
'!OPT=4

dim test(0 to 3) as ubyte => {1,2,3,4} at $C000

'this should return 1
print at 0,0;peek($c000)

do
loop until inkey$<>""

This is a bug in the sense that the compiler should report a syntax error.

It's not allowed to initialize an array with DIM AT (i.e. what if you initialize it into a ROM address?).
Allocation at a given memory address is not allowed (unless you declare asm code with ORG, which is NOT recommended).
Declaring things at given locations will be done outside the compiler (with a linker, and config files, and compiling to .obj, etc).

It's an effort that will take time, be patient, since this is required also for pagination, and interruptions.
Implementing things like this would make the compiler very architecture-dependent, and I want to move to a multi-architecture scheme.

Thank you for the response, that makes perfect sense.

[boriel]

Try this beta. It will prevent you to do this with a Syntax Error.
http://www.boriel.com/files/zxb/zxbasic-...a11.tar.gz
http://www.boriel.com/files/zxb/zxbasic-...beta11.zip
http://www.boriel.com/files/zxb/zxbasic-...-win32.zip
http://www.boriel.com/files/zxb/zxbasic-...x64.tar.gz
http://www.boriel.com/files/zxb/zxbasic-...cos.tar.gz

[Ljg701]

Try this beta. It will prevent you to do this with a Syntax Error.
http://www.boriel.com/files/zxb/zxbasic-...a11.tar.gz
http://www.boriel.com/files/zxb/zxbasic-...beta11.zip
http://www.boriel.com/files/zxb/zxbasic-...-win32.zip
http://www.boriel.com/files/zxb/zxbasic-...x64.tar.gz
http://www.boriel.com/files/zxb/zxbasic-...cos.tar.gz

That indeed seems to prevent the scenario.