<![CDATA[Boriel Basic Forum - Bug Reports]]> https://forum.boriel.com/ Fri, 15 May 2026 14:59:26 +0000 MyBB <![CDATA[[SOLVED] Array layout bug - regression in 1.18.3]]> https://forum.boriel.com/showthread.php?tid=2645 Fri, 24 Oct 2025 22:24:41 +0000 Zoran]]> https://forum.boriel.com/showthread.php?tid=2645

Code:
dim a(5) as ubyte => {0, 1, 2, 3, 4, 5}
dim b(5) as ubyte
dim i as uinteger

for i = 0 to 5
    poke @b + i, a(i)
next

cls

for i = 0 to 5
    print a(i), b(i)
next

When compiled with zxbasic 1.18.2 this works as expected - both arrays are same. See the attached image:

.png   arrays_zxbasic_1_18_2.png (Size: 8.81 KB / Downloads: 178)
However, with zxbasic 1.18.3, the programme fails miserably and crashes the Spectrum

In both cases compiled with 
Quote: Wrote:--optimize 2  --output-format=tzx --BASIC --autorun --explicit --strict

Now, this is the simple case made to illustrate the bug. The main problem I have is with character arrays -- I have custom font with cyrilic letters designed in ZXBasicStudio, stored as two dimensional array (95, 7) -- when I want to write cyrilic text I poke the system variable 5C36 to the address of the array minus 256 (@array - $100) and when I want to print latin text, I just poke this variable back to default value  $3C00. This worked perfectly until version 1.18.3 came out. Now, everything is broken, as the characters in the array are obviously not stored continuously in memory.
What happend with array layout?



Now I tried to see the address of the array itself, compared with the addresses of array elements:
Code:
dim a(5) as ubyte => {0, 1, 2, 3, 4, 5}
dim i as uinteger
cls
print "@a = "; @a
print "------------"
for i = 0 to 5
  print "@a("; i; ") = "; @a(i)
next

The attached image shows the output with zxbasic 1.18.2 compared with zxbasic 1.18.3:

.png   arrayAddresses.png (Size: 14.42 KB / Downloads: 208)

It seems that in zxbasic 1.18.3, there are eight bytes between the address of the array itself (@a) and the first element (@a(0) ). The array elements are stored continuously after all.

So, I can workaround the problem with the custom character set that I mentioned in my previous post using:
Code:
poke (uinteger $5c36, @charset(0,0) - $100) ' the address of the first element
instead of
Code:
poke (uinteger $5c36, @charset - $0100) ' the address of the array

But still, is there a reason for this, or is it just a bug?]]>

Code:
dim a(5) as ubyte => {0, 1, 2, 3, 4, 5}
dim b(5) as ubyte
dim i as uinteger

for i = 0 to 5
    poke @b + i, a(i)
next

cls

for i = 0 to 5
    print a(i), b(i)
next

When compiled with zxbasic 1.18.2 this works as expected - both arrays are same. See the attached image:

.png   arrays_zxbasic_1_18_2.png (Size: 8.81 KB / Downloads: 178)
However, with zxbasic 1.18.3, the programme fails miserably and crashes the Spectrum

In both cases compiled with 
Quote: Wrote:--optimize 2  --output-format=tzx --BASIC --autorun --explicit --strict

Now, this is the simple case made to illustrate the bug. The main problem I have is with character arrays -- I have custom font with cyrilic letters designed in ZXBasicStudio, stored as two dimensional array (95, 7) -- when I want to write cyrilic text I poke the system variable 5C36 to the address of the array minus 256 (@array - $100) and when I want to print latin text, I just poke this variable back to default value  $3C00. This worked perfectly until version 1.18.3 came out. Now, everything is broken, as the characters in the array are obviously not stored continuously in memory.
What happend with array layout?



Now I tried to see the address of the array itself, compared with the addresses of array elements:
Code:
dim a(5) as ubyte => {0, 1, 2, 3, 4, 5}
dim i as uinteger
cls
print "@a = "; @a
print "------------"
for i = 0 to 5
  print "@a("; i; ") = "; @a(i)
next

The attached image shows the output with zxbasic 1.18.2 compared with zxbasic 1.18.3:

.png   arrayAddresses.png (Size: 14.42 KB / Downloads: 208)

It seems that in zxbasic 1.18.3, there are eight bytes between the address of the array itself (@a) and the first element (@a(0) ). The array elements are stored continuously after all.

So, I can workaround the problem with the custom character set that I mentioned in my previous post using:
Code:
poke (uinteger $5c36, @charset(0,0) - $100) ' the address of the first element
instead of
Code:
poke (uinteger $5c36, @charset - $0100) ' the address of the array

But still, is there a reason for this, or is it just a bug?]]> <![CDATA[ZX Basic Studio Bugs]]> https://forum.boriel.com/showthread.php?tid=2638 Fri, 19 Sep 2025 15:21:36 +0000 ZXPeter]]> https://forum.boriel.com/showthread.php?tid=2638
This post relates to ZX Basic Studio builds 1.0.8702.19933 2023-10-29 and 1.5.9168.37638 2025-02-06 which ,for brevity, I shall call buildA and buildB respectively.

Following the instructions for creating a project from pages 47 to 53 of the "Boriel Basic for ZX Spectrum" book I have the following observations:

(1)
With buildA the Main.bas file appears in the explorer window when it is created,as described in the book. 

With buildB it does not. Closing the displayed code by clicking the X next to the "Main.bas" file name removes the code from view and there is no way of re-opening 
it from the explorer window (as it isn't listed there). One way to make the file name visible in the explorer window is to close then re-open the project.

(2)
For both buildA and buildB running the book's example code (page 51) without debug results in the expected coloured block of X's.
Running the code under debug with a breakpoint set as shown on page 52, neither build produces the full block (stops after 3 and a bit rows).

Hope this information is useful.]]>
This post relates to ZX Basic Studio builds 1.0.8702.19933 2023-10-29 and 1.5.9168.37638 2025-02-06 which ,for brevity, I shall call buildA and buildB respectively.

Following the instructions for creating a project from pages 47 to 53 of the "Boriel Basic for ZX Spectrum" book I have the following observations:

(1)
With buildA the Main.bas file appears in the explorer window when it is created,as described in the book. 

With buildB it does not. Closing the displayed code by clicking the X next to the "Main.bas" file name removes the code from view and there is no way of re-opening 
it from the explorer window (as it isn't listed there). One way to make the file name visible in the explorer window is to close then re-open the project.

(2)
For both buildA and buildB running the book's example code (page 51) without debug results in the expected coloured block of X's.
Running the code under debug with a breakpoint set as shown on page 52, neither build produces the full block (stops after 3 and a bit rows).

Hope this information is useful.]]> <![CDATA[Strange Happenings]]> https://forum.boriel.com/showthread.php?tid=2625 Wed, 07 May 2025 09:05:06 +0000 zedex82]]> https://forum.boriel.com/showthread.php?tid=2625
I have noticed two things.

1. Any new file I create is not showing in the Project Explorer. I have to reload the project for them to appear

2. I have left all the colours in the Coding window as default so the main commands are shown in blue. When I type ENDIF it does not change to blue but remains white.

The laptop I am using is a spare one (windows 10) that I take away with me and I have never installed ZXBasic Studio or Boriel before and I do not have my main laptop to check if it is the laptop or not.

Thanks

ZeD]]>
I have noticed two things.

1. Any new file I create is not showing in the Project Explorer. I have to reload the project for them to appear

2. I have left all the colours in the Coding window as default so the main commands are shown in blue. When I type ENDIF it does not change to blue but remains white.

The laptop I am using is a spare one (windows 10) that I take away with me and I have never installed ZXBasic Studio or Boriel before and I do not have my main laptop to check if it is the laptop or not.

Thanks

ZeD]]> <![CDATA[Scope rules]]> https://forum.boriel.com/showthread.php?tid=2620 Thu, 03 Apr 2025 13:54:55 +0000 Zoran]]> https://forum.boriel.com/showthread.php?tid=2620
I wanted to test if the variable declared in outer routine is accessible from the inner routine (I couldn't find it documented anywhere).


Please see these two simple examples which show quite different behaviour.

Both compiled with Zx Basic version 1.17.3, with these options:


Quote:--optimize 2 -f tzx --BASIC --autorun --explicit --strict

The first example:

Code:
#pragma explicit = true
#pragma strict = true

sub outerRoutine
    dim n as ubyte
   
    sub nestedRoutine()
        print "From inner sub, before: "; n
        n = 22
        print "From inner sub, after: "; n
    end sub
   
    n = 11
   
    print "From outer sub, before: "; n
    nestedRoutine()
    print "From outer sub, after: "; n
end sub

cls
outerRoutine()


The output:

Quote:From outer sub, before: 11
From inner sub, before: 11
From inner sub, after: 22
From outer sub, after: 22


So the first example shows that variable n, declared in outer routine is fully accessible from the nested routine.

In the second example, I only added a dummy variable declaration inside the nested routine:

Code:
#pragma explicit = true
#pragma strict = true

sub outerRoutine
    dim n as ubyte
   
    sub nestedRoutine()
        dim k as ubyte ' declare a dummy variable
        if k <> 0 then ' and access it
            print "";  ' do nothing meaningful
        end if
       
        print "From inner sub, before: "; n
        n = 22
        print "From inner sub, after: "; n
    end sub
   
    n = 11
   
    print "From outer sub, before: "; n
    nestedRoutine()
    print "From outer sub, after: "; n
end sub

cls
outerRoutine()

Quote:From outer sub, before: 11
From inner sub, before: 0
From inner sub, after: 22
From outer sub, after: 11

Totally different output!
The main problem is that, referring to variable n, something is accessed and even written to inside the nested subroutine, but it is clearly not the varible n declared above.

With explicit and strict options, if the outer routine scope is not accessible, the compiler has to give an error that variable n is not declared in routine innerRoutine.
The compiler gives no error, though. Then the programme behaviour is unpredictable and rather dangerous actually.]]>
I wanted to test if the variable declared in outer routine is accessible from the inner routine (I couldn't find it documented anywhere).


Please see these two simple examples which show quite different behaviour.

Both compiled with Zx Basic version 1.17.3, with these options:


Quote:--optimize 2 -f tzx --BASIC --autorun --explicit --strict

The first example:

Code:
#pragma explicit = true
#pragma strict = true

sub outerRoutine
    dim n as ubyte
   
    sub nestedRoutine()
        print "From inner sub, before: "; n
        n = 22
        print "From inner sub, after: "; n
    end sub
   
    n = 11
   
    print "From outer sub, before: "; n
    nestedRoutine()
    print "From outer sub, after: "; n
end sub

cls
outerRoutine()


The output:

Quote:From outer sub, before: 11
From inner sub, before: 11
From inner sub, after: 22
From outer sub, after: 22


So the first example shows that variable n, declared in outer routine is fully accessible from the nested routine.

In the second example, I only added a dummy variable declaration inside the nested routine:

Code:
#pragma explicit = true
#pragma strict = true

sub outerRoutine
    dim n as ubyte
   
    sub nestedRoutine()
        dim k as ubyte ' declare a dummy variable
        if k <> 0 then ' and access it
            print "";  ' do nothing meaningful
        end if
       
        print "From inner sub, before: "; n
        n = 22
        print "From inner sub, after: "; n
    end sub
   
    n = 11
   
    print "From outer sub, before: "; n
    nestedRoutine()
    print "From outer sub, after: "; n
end sub

cls
outerRoutine()

Quote:From outer sub, before: 11
From inner sub, before: 0
From inner sub, after: 22
From outer sub, after: 11

Totally different output!
The main problem is that, referring to variable n, something is accessed and even written to inside the nested subroutine, but it is clearly not the varible n declared above.

With explicit and strict options, if the outer routine scope is not accessible, the compiler has to give an error that variable n is not declared in routine innerRoutine.
The compiler gives no error, though. Then the programme behaviour is unpredictable and rather dangerous actually.]]> <![CDATA[Spectrum keywords codes]]> https://forum.boriel.com/showthread.php?tid=2618 Fri, 07 Mar 2025 20:01:17 +0000 Zoran]]> https://forum.boriel.com/showthread.php?tid=2618
The documentation for CHR function (https://zxbasic.readthedocs.io/en/latest/chr/) says that, although expanded, the function is 100% Sinclair basic compatible.
If it is so, then for the same parameters I'd expect the same output, not only for ascii letters, but also for sinclair basic keywords.

In Sinclair basic, this programme:

Code:
10 CLS
20 FOR i = 230 TO 250
30 PRINT CHR$ i
40 NEXT i

gives some Basic keywords in the output (see the attached image zxkeywords_sinclair.png).

.png   zxkeywords_sinclair.png (Size: 10.26 KB / Downloads: 946)

The equivalent programme in ZX Basic:
Code:
dim i as ubyte

cls
for i = 230 to 250
    print chr(i)
next

outputs some silly characters (see the attached image zxkeywords_boriel.png).

.png   zxkeywords_boriel.png (Size: 11.44 KB / Downloads: 928)

Compiled with:
Quote:..\..\zxbasic\zxbc.exe --optimize 2 --output zxkeywords.tzx --output-format tzx --BASIC --autorun --explicit --strict zxkeywords.bas

I'd say it is a bug.]]>
The documentation for CHR function (https://zxbasic.readthedocs.io/en/latest/chr/) says that, although expanded, the function is 100% Sinclair basic compatible.
If it is so, then for the same parameters I'd expect the same output, not only for ascii letters, but also for sinclair basic keywords.

In Sinclair basic, this programme:

Code:
10 CLS
20 FOR i = 230 TO 250
30 PRINT CHR$ i
40 NEXT i

gives some Basic keywords in the output (see the attached image zxkeywords_sinclair.png).

.png   zxkeywords_sinclair.png (Size: 10.26 KB / Downloads: 946)

The equivalent programme in ZX Basic:
Code:
dim i as ubyte

cls
for i = 230 to 250
    print chr(i)
next

outputs some silly characters (see the attached image zxkeywords_boriel.png).

.png   zxkeywords_boriel.png (Size: 11.44 KB / Downloads: 928)

Compiled with:
Quote:..\..\zxbasic\zxbc.exe --optimize 2 --output zxkeywords.tzx --output-format tzx --BASIC --autorun --explicit --strict zxkeywords.bas

I'd say it is a bug.]]> <![CDATA[Using constants not allowed in DATAs]]> https://forum.boriel.com/showthread.php?tid=2615 Mon, 03 Mar 2025 21:10:00 +0000 baltasarq]]> https://forum.boriel.com/showthread.php?tid=2615 Another bug or at least improvement, sorry!
When I create constants, such as:
const DCMD_EOD                            as ubyte = 100
const DCMD_LINE                           as ubyte = 101
const DCMD_CIRCLE                         as ubyte = 102
const DCMD_FILL                           as ubyte = 103
const DCMD_UDG                            as ubyte = 104

And then try to use them like so (initializer expression):
sub draw_presentation()
    dim pic_data(11) as ubyte => { _
        DCMD_Circle, 50, 180, 10,  _
        DCMD_Fill, 50, 180,        _
        DCMD_Circle, 100, 160, 25, _
        DCMD_EOD }
   
    draw_pic( pic_data )
end sub

Or maybe like so (DATAs):
LocPics:
    ' Loc 0 - Limbo
    data DCMD_Line, 0, 180, 250, 100, _
        DCMD_Line, 250, 180, 0, 100, _
        DCMD_EOD

    ' Loc 1 - Landing
    data DCMD_Circle, 50, 180, 10,  _
        DCMD_Fill, 50, 180,        _
        DCMD_Circle, 100, 160, 25,  _
        DCMD_EOD

I receive the following errors:
For the use of constants inside DATAs:
locs.bas:64: warning: [W100] Using default implicit type 'float' for 'DCMD_Line'
locs.bas:69: warning: [W100] Using default implicit type 'float' for 'DCMD_Circle'
locs.bas:70: warning: [W100] Using default implicit type 'float' for 'DCMD_Fill'

This doesn't make any sense, since they are defined as constants of type ubyte.
For the use of these constants inside the constant initializer for an array:
reveni.bas:14: error: Initializer expression is not constant.
reveni.bas:19: warning: [W100] Using default implicit type 'float' for 'pic_data'
reveni.bas:19: error: Invalid argument 'pic_data'

Again, this doesn't make any sense, since they are constants but the initializer expression is erroneously detected as non-constant.
Could this be solved?
Thanks,]]> Another bug or at least improvement, sorry!
When I create constants, such as:
const DCMD_EOD                            as ubyte = 100
const DCMD_LINE                           as ubyte = 101
const DCMD_CIRCLE                         as ubyte = 102
const DCMD_FILL                           as ubyte = 103
const DCMD_UDG                            as ubyte = 104

And then try to use them like so (initializer expression):
sub draw_presentation()
    dim pic_data(11) as ubyte => { _
        DCMD_Circle, 50, 180, 10,  _
        DCMD_Fill, 50, 180,        _
        DCMD_Circle, 100, 160, 25, _
        DCMD_EOD }
   
    draw_pic( pic_data )
end sub

Or maybe like so (DATAs):
LocPics:
    ' Loc 0 - Limbo
    data DCMD_Line, 0, 180, 250, 100, _
        DCMD_Line, 250, 180, 0, 100, _
        DCMD_EOD

    ' Loc 1 - Landing
    data DCMD_Circle, 50, 180, 10,  _
        DCMD_Fill, 50, 180,        _
        DCMD_Circle, 100, 160, 25,  _
        DCMD_EOD

I receive the following errors:
For the use of constants inside DATAs:
locs.bas:64: warning: [W100] Using default implicit type 'float' for 'DCMD_Line'
locs.bas:69: warning: [W100] Using default implicit type 'float' for 'DCMD_Circle'
locs.bas:70: warning: [W100] Using default implicit type 'float' for 'DCMD_Fill'

This doesn't make any sense, since they are defined as constants of type ubyte.
For the use of these constants inside the constant initializer for an array:
reveni.bas:14: error: Initializer expression is not constant.
reveni.bas:19: warning: [W100] Using default implicit type 'float' for 'pic_data'
reveni.bas:19: error: Invalid argument 'pic_data'

Again, this doesn't make any sense, since they are constants but the initializer expression is erroneously detected as non-constant.
Could this be solved?
Thanks,]]> <![CDATA[Download links broken]]> https://forum.boriel.com/showthread.php?tid=2613 Mon, 17 Feb 2025 02:03:46 +0000 xthunderheartx@gmail.com]]> https://forum.boriel.com/showthread.php?tid=2613
Thanks - Dallas]]>
Thanks - Dallas]]> <![CDATA[2D Array Errors]]> https://forum.boriel.com/showthread.php?tid=2610 Thu, 13 Feb 2025 15:42:14 +0000 raymondlesley]]> https://forum.boriel.com/showthread.php?tid=2610
The compiler supports multi-dimensional arrays, but it throws an error if I attempt to get a "slice" of the data.

My code:

Code:
DIM data_array(0 TO 2, 0 TO 3) AS UByte = { _
    {0, 1, 2, 3}, {4, 5, 6, 7}, {8, 9, 10, 11} _
}

DIM element12 AS UByte = data_array(1, 2)

DIM element0(0 TO 3) AS UByte

element0 = data_array(0)  ' throws an error

I get no errors relating to element12
I would expect that element0 should result in {0, 1, 2, 3}. It's the right "shape". Instead I get an error:

Quote:
array_test.bas:9: error: Syntax Error. Unexpected token '(' <LP>

I've tried variants e.g. data_array(0, : ) or data_array(0,0 TO 3). Nothing seems to work.

I'm using ZX BASIC 1.17.2]]>
The compiler supports multi-dimensional arrays, but it throws an error if I attempt to get a "slice" of the data.

My code:

Code:
DIM data_array(0 TO 2, 0 TO 3) AS UByte = { _
    {0, 1, 2, 3}, {4, 5, 6, 7}, {8, 9, 10, 11} _
}

DIM element12 AS UByte = data_array(1, 2)

DIM element0(0 TO 3) AS UByte

element0 = data_array(0)  ' throws an error

I get no errors relating to element12
I would expect that element0 should result in {0, 1, 2, 3}. It's the right "shape". Instead I get an error:

Quote:
array_test.bas:9: error: Syntax Error. Unexpected token '(' <LP>

I've tried variants e.g. data_array(0, : ) or data_array(0,0 TO 3). Nothing seems to work.

I'm using ZX BASIC 1.17.2]]> <![CDATA[Breaking loops]]> https://forum.boriel.com/showthread.php?tid=2608 Fri, 07 Feb 2025 12:28:26 +0000 baltasarq]]> https://forum.boriel.com/showthread.php?tid=2608
Code:
for i = 0 to ubound(m)
    if m( i ) = 0
        break
    end if
next

At first, I did not understand what was happening. break was not working. But there was not any error or even a warning. Then I realized: break is not a part of Basic. It never was.
The strange point is the absence of any error or warning. Either this was included in the grammar by error, or maybe because it is planned for inclusion.
I don't know.]]>
Code:
for i = 0 to ubound(m)
    if m( i ) = 0
        break
    end if
next

At first, I did not understand what was happening. break was not working. But there was not any error or even a warning. Then I realized: break is not a part of Basic. It never was.
The strange point is the absence of any error or warning. Either this was included in the grammar by error, or maybe because it is planned for inclusion.
I don't know.]]> <![CDATA[Colors only shown... sometimes?]]> https://forum.boriel.com/showthread.php?tid=2595 Tue, 07 Jan 2025 13:21:21 +0000 baltasarq]]> https://forum.boriel.com/showthread.php?tid=2595
I'm using print64.bas, and the code I'm using to show a command menu is as follows:

Code:
const COLOR_BLACK            as ubyte = 0
const COLOR_BLUE              as ubyte = 1
const COLOR_RED              as ubyte = 2
const COLOR_MAGENTA          as ubyte = 3
const COLOR_GREEN            as ubyte = 4
const COLOR_CYAN              as ubyte = 5
const COLOR_YELLOW            as ubyte = 6
const COLOR_WHITE            as ubyte = 7


sub cursor_to(row as ubyte, col as ubyte)
    printat64( row, col )
end sub


sub cprint(s as string)
    print64( s )
end sub


sub lf()
    cprint( CR )
end sub


sub set_colors(i as ubyte, p as ubyte)
    paper( p )
    ink( i )
end sub


sub set_default_colors()
    set_colors( COLOR_WHITE, COLOR_BLACK )
end sub


sub set_highlighted_colors()
    set_colors( COLOR_CYAN, COLOR_BLACK )
end sub


sub set_action_colors()
    set_colors( COLOR_YELLOW, COLOR_BLACK )
end sub


sub print_word_marked_initial(word as string)
    set_action_colors()
    cprint( word( 0 ) )
    set_default_colors()
    cprint( word( 1 to ) )
end sub


sub print_cmds()
' Print basic options
cursor_to( SCR_FIRST_LINE_CMDS, 0 )
print_word_marked_initial( "Inv " )
print_word_marked_initial( "Mira alrededor " )
cprint( "E" ): print_word_marked_initial( "xamina... " )
print_word_marked_initial( "Norte " )
print_word_marked_initial( "Sur " )
print_word_marked_initial( "Este " )
print_word_marked_initial( "Oeste " )
print_word_marked_initial( "Arriba " )
cprint( "A" )
        print_word_marked_initial( "bajo" )
        lf()

' Print object manipulation options
print_word_marked_initial( "Coge... " )
print_word_marked_initial( "Deja... " )
cprint( "Em" ): print_word_marked_initial( "puja... " )
print_word_marked_initial( "Tira de... " )
print_word_marked_initial( "Rompe... " )
end sub

Well, the code should be straightforward. I also know it should work because I ported it from C, the same source code I used wtith z88dk. Unfortunately, it does not work, or it does not always work... (check the image).

What could be wrong?

-- Baltasar

.png   speccy_reveni_cmds.png (Size: 4.33 KB / Downloads: 549) ]]>
I'm using print64.bas, and the code I'm using to show a command menu is as follows:

Code:
const COLOR_BLACK            as ubyte = 0
const COLOR_BLUE              as ubyte = 1
const COLOR_RED              as ubyte = 2
const COLOR_MAGENTA          as ubyte = 3
const COLOR_GREEN            as ubyte = 4
const COLOR_CYAN              as ubyte = 5
const COLOR_YELLOW            as ubyte = 6
const COLOR_WHITE            as ubyte = 7


sub cursor_to(row as ubyte, col as ubyte)
    printat64( row, col )
end sub


sub cprint(s as string)
    print64( s )
end sub


sub lf()
    cprint( CR )
end sub


sub set_colors(i as ubyte, p as ubyte)
    paper( p )
    ink( i )
end sub


sub set_default_colors()
    set_colors( COLOR_WHITE, COLOR_BLACK )
end sub


sub set_highlighted_colors()
    set_colors( COLOR_CYAN, COLOR_BLACK )
end sub


sub set_action_colors()
    set_colors( COLOR_YELLOW, COLOR_BLACK )
end sub


sub print_word_marked_initial(word as string)
    set_action_colors()
    cprint( word( 0 ) )
    set_default_colors()
    cprint( word( 1 to ) )
end sub


sub print_cmds()
' Print basic options
cursor_to( SCR_FIRST_LINE_CMDS, 0 )
print_word_marked_initial( "Inv " )
print_word_marked_initial( "Mira alrededor " )
cprint( "E" ): print_word_marked_initial( "xamina... " )
print_word_marked_initial( "Norte " )
print_word_marked_initial( "Sur " )
print_word_marked_initial( "Este " )
print_word_marked_initial( "Oeste " )
print_word_marked_initial( "Arriba " )
cprint( "A" )
        print_word_marked_initial( "bajo" )
        lf()

' Print object manipulation options
print_word_marked_initial( "Coge... " )
print_word_marked_initial( "Deja... " )
cprint( "Em" ): print_word_marked_initial( "puja... " )
print_word_marked_initial( "Tira de... " )
print_word_marked_initial( "Rompe... " )
end sub

Well, the code should be straightforward. I also know it should work because I ported it from C, the same source code I used wtith z88dk. Unfortunately, it does not work, or it does not always work... (check the image).

What could be wrong?

-- Baltasar

.png   speccy_reveni_cmds.png (Size: 4.33 KB / Downloads: 549) ]]> <![CDATA[strange behaviour of raise to power]]> https://forum.boriel.com/showthread.php?tid=2593 Sun, 05 Jan 2025 12:53:33 +0000 jjluke65]]> https://forum.boriel.com/showthread.php?tid=2593
DIM x1, x2 AS float
x1 = -3
x2 = x1^2
PRINT x2


if x1 = 3 (or any positive number) the correct result (9) is printed.
If x1 = -3  I get no result in the output (nothing is printed on the screen) and no message is shown.
I've tried to define x1 and x2 as integer, with the same problem.
I'm using 1.17.3 version with ZX Basic Studio, but I also tried with Visual Studio Code and Fuse (same result).
I'm doing something wrong or it's a bug?
Thanks]]>
DIM x1, x2 AS float
x1 = -3
x2 = x1^2
PRINT x2


if x1 = 3 (or any positive number) the correct result (9) is printed.
If x1 = -3  I get no result in the output (nothing is printed on the screen) and no message is shown.
I've tried to define x1 and x2 as integer, with the same problem.
I'm using 1.17.3 version with ZX Basic Studio, but I also tried with Visual Studio Code and Fuse (same result).
I'm doing something wrong or it's a bug?
Thanks]]> <![CDATA[pascalated boriel zx basic for the spectrum (*solved*)]]> https://forum.boriel.com/showthread.php?tid=2591 Tue, 31 Dec 2024 09:13:10 +0000 funkheld]]> https://forum.boriel.com/showthread.php?tid=2591 will the tap program be faster with this new Pascal or is it just an optical design for the eye?

https://arcalusitana.org/MuseuZX/Pascalated_ZXBASIC/

Thanks.
greeting]]> will the tap program be faster with this new Pascal or is it just an optical design for the eye?

https://arcalusitana.org/MuseuZX/Pascalated_ZXBASIC/

Thanks.
greeting]]> <![CDATA[Compiler gives strange error message (solved)]]> https://forum.boriel.com/showthread.php?tid=2590 Sun, 29 Dec 2024 22:31:54 +0000 baltasarq]]> https://forum.boriel.com/showthread.php?tid=2590
Code:
reveni.bas:46: error: Can't convert non-numeric value to string at compile time
reveni.bas:44: error: Can't convert non-numeric value to string at compile time
The second error is signaling a line that... is empty! The first error refers to the following source:
Code:
clrscr()
I think this means that the compiler gets somehow confused about something. I'm attaching the project.
Thanks,
-- Baltasar

.zip   reveni.zip (Size: 12.2 KB / Downloads: 521) ]]>
Code:
reveni.bas:46: error: Can't convert non-numeric value to string at compile time
reveni.bas:44: error: Can't convert non-numeric value to string at compile time
The second error is signaling a line that... is empty! The first error refers to the following source:
Code:
clrscr()
I think this means that the compiler gets somehow confused about something. I'm attaching the project.
Thanks,
-- Baltasar

.zip   reveni.zip (Size: 12.2 KB / Downloads: 521) ]]> <![CDATA[Compiler crash (solved)]]> https://forum.boriel.com/showthread.php?tid=2587 Sun, 15 Dec 2024 20:54:36 +0000 baltasarq]]> https://forum.boriel.com/showthread.php?tid=2587
Code:
$ python ~/bin/zxbasic/zxbc.py --tap --BASIC --autorun reveni.bas
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:50: warning: [W150] Parameter 'scancode' is never used
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/print64.bas:20: warning: [W150] Parameter 'characters' is never used
cmd.bas:41: warning: [W150] Parameter 'cmd' is never used
io.bas:222: warning: [W100] Using default implicit type 'float' for 'current_loc'
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:51: warning: [W190] Function 'MultiKeys' should return a value
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:72: warning: [W190] Function 'GetKeyScanCode' should return a value
objs.bas:88: warning: [W170] Function 'get_objs_in' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:50: warning: [W170] Function 'MultiKeys' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:71: warning: [W170] Function 'GetKeyScanCode' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:29: warning: [W170] Function 'mid' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:40: warning: [W170] Function 'left' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:51: warning: [W170] Function 'right' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:98: warning: [W170] Function 'strpos' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:124: warning: [W170] Function 'ucase2' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:174: warning: [W170] Function 'ucase' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:249: warning: [W170] Function 'ltrim' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:275: warning: [W170] Function 'rtrim' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:304: warning: [W170] Function 'trim' is never called and has been ignored
util.bas:47: warning: [W170] Function 'testMultiplyStr' is never called and has been ignored
util.bas:57: warning: [W170] Function 'testFormatStr' is never called and has been ignored
Traceback (most recent call last):
  File "/home/baltasarq/bin/zxbasic/zxbc.py", line 12, in <module>
    sys.exit(zxbc.main())  # Exit
            ^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/zxbc/zxbc.py", line 110, in main
    optimizer.visit(zxbparser.ast)
  File "/home/baltasarq/bin/zxbasic/src/api/optimize.py", line 199, in visit
    return super().visit(node)
          ^^^^^^^^^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/api/optimize.py", line 56, in visit
    return super().visit(ToVisit(node))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/ast/ast.py", line 42, in visit
    stack.append(last.send(last_result))
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/api/optimize.py", line 423, in visit_FOR
    if from_ > to_ and step_ > 0:
      ^^^^^^^^^^^
TypeError: '>' not supported between instances of 'SymbolID' and 'SymbolID'

-- Baltasar

.zip   reveni.zip (Size: 11.6 KB / Downloads: 551) ]]>
Code:
$ python ~/bin/zxbasic/zxbc.py --tap --BASIC --autorun reveni.bas
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:50: warning: [W150] Parameter 'scancode' is never used
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/print64.bas:20: warning: [W150] Parameter 'characters' is never used
cmd.bas:41: warning: [W150] Parameter 'cmd' is never used
io.bas:222: warning: [W100] Using default implicit type 'float' for 'current_loc'
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:51: warning: [W190] Function 'MultiKeys' should return a value
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:72: warning: [W190] Function 'GetKeyScanCode' should return a value
objs.bas:88: warning: [W170] Function 'get_objs_in' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:50: warning: [W170] Function 'MultiKeys' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/keys.bas:71: warning: [W170] Function 'GetKeyScanCode' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:29: warning: [W170] Function 'mid' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:40: warning: [W170] Function 'left' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:51: warning: [W170] Function 'right' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:98: warning: [W170] Function 'strpos' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:124: warning: [W170] Function 'ucase2' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:174: warning: [W170] Function 'ucase' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:249: warning: [W170] Function 'ltrim' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:275: warning: [W170] Function 'rtrim' is never called and has been ignored
/home/baltasarq/bin/zxbasic/src/lib/arch/zx48k/stdlib/string.bas:304: warning: [W170] Function 'trim' is never called and has been ignored
util.bas:47: warning: [W170] Function 'testMultiplyStr' is never called and has been ignored
util.bas:57: warning: [W170] Function 'testFormatStr' is never called and has been ignored
Traceback (most recent call last):
  File "/home/baltasarq/bin/zxbasic/zxbc.py", line 12, in <module>
    sys.exit(zxbc.main())  # Exit
            ^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/zxbc/zxbc.py", line 110, in main
    optimizer.visit(zxbparser.ast)
  File "/home/baltasarq/bin/zxbasic/src/api/optimize.py", line 199, in visit
    return super().visit(node)
          ^^^^^^^^^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/api/optimize.py", line 56, in visit
    return super().visit(ToVisit(node))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/ast/ast.py", line 42, in visit
    stack.append(last.send(last_result))
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/baltasarq/bin/zxbasic/src/api/optimize.py", line 423, in visit_FOR
    if from_ > to_ and step_ > 0:
      ^^^^^^^^^^^
TypeError: '>' not supported between instances of 'SymbolID' and 'SymbolID'

-- Baltasar

.zip   reveni.zip (Size: 11.6 KB / Downloads: 551) ]]> <![CDATA[Better parameters mismatch function (solved)]]> https://forum.boriel.com/showthread.php?tid=2582 Fri, 13 Dec 2024 21:29:52 +0000 baltasarq]]> https://forum.boriel.com/showthread.php?tid=2582
Code:
util.bas:105: error: Function 'FormatStr' takes 3 parameters, not 1
This message was correct, but instead of signaling the file name and the line where the error was present, it was showing the line number and the file name of where the function was defined!
It also messes with the line number, which corresponds to where the error happened, not where the function was defined. In my case, the error happened at line number 105 of player.bas, calling function FormatStr() defined in line number 39 of util.bas.
I think it would be better to expose both pieces of information, maybe this way:
Code:
player.bas: 105: error: Function 'FormatStr' takes 3 parameters, not 1
util.bas:39: error: Function 'FormatStr' defined here.
Well, something like that.]]>
Code:
util.bas:105: error: Function 'FormatStr' takes 3 parameters, not 1
This message was correct, but instead of signaling the file name and the line where the error was present, it was showing the line number and the file name of where the function was defined!
It also messes with the line number, which corresponds to where the error happened, not where the function was defined. In my case, the error happened at line number 105 of player.bas, calling function FormatStr() defined in line number 39 of util.bas.
I think it would be better to expose both pieces of information, maybe this way:
Code:
player.bas: 105: error: Function 'FormatStr' takes 3 parameters, not 1
util.bas:39: error: Function 'FormatStr' defined here.
Well, something like that.]]>