This program was posted on the WOS forums:

Hi all

Long time no see around here :oops: but now I'm getting some free time to spend with ZX Basic, so I hope to come more often
In fact, I have a question: I want to store a label name in a variable, in order to do GOSUBs using a var, not fixed names. I made this code so far, but it fails with the message 'identifier 'eti$' is a var, not a label':

I don´t know about the default strings, but old compilers had options to select string length, my question is about effect of retail length of strings. Example: DefaultShort=8 chars DefaultLong=32 chars.
What do you think of this?

So, I found some glitches again.
1. In Optimisation modes when procedures (e.g. dummy procedures for ASM containers as used in BeepFX) are not called, ZXBC shows a warning that procedures are not used, but exit with exitcode 1 (Error).
2. Assigning part of String variables do not work. Compiler says, Variable is not Array, but in Sinclair BASIC it works. This example changes string "Test188" to "Tezt188".

Hi Boriel.
The Address of a label or variable is afaik a constant (@label/@variable), so I wonder why it is not possible to use it in the DIM:

I'm currently working on a survival horror game for the Spectrum. Today posted two screenshots of the game in my forum:
<!-- m --><a class="postlink" href="http://lcd.forenworld.at/viewtopic.php?f=14&t=32">http://lcd.forenworld.at/viewtopic.php?f=14&t=32</a><!-- m -->
Yumiko is not Nanako! Yumiko has no sex appeal. And Yumiko is not alone in a haunted mansion...
The lightning effect is working well and fast enough. The game mechanic is finished until I can find some bugs, and no levels designed yet.
The "Death" sequence is disturbing, I promise! Imagine a tentacle grabing this girl foot and pulling her out of the visible field.
Yumiko game is not suitable for children who fear darkness! In fact even some adult had nightmares after playing the test level. I had not a good feeling to let a little girl walking alone in a nightie in a demonic mansion at night, but it looks like it works .

I've searched the forums about this issue but I haven't found anything.

I gather that RANDOMIZE uses the timer to seed the variable, doesn't it? So this program, depending on the time I take to press the key, should render different numbers. Well, the result is always 6.

also started the msx version as well - the .rom file is created fine, but i still don't know why the .rom file isn't running on OpenMSX - if someone know, please let me know!

for now, the idea is to support msx1, msx2, msx2+, and gfx9000 in the libraries - and having zxbasic-compiler as an useful tool for creating stuff like for contests like msxdev (for this year, the deadline is at november 30! )

Attached Files

  example01_msx_zxbasic.zip (Size: 18.6 KB / Downloads: 1196)

Boriel asked me to ask you all here, and i think it's not so offtopic (i don't know where else to ask it, since it's not a technical question)

as far as we may need to create groups about zxbasic-compiler, like at identi.ca, twitter, facebook, create a favicon for this project, etc. - maybe we need a icon/logomark for this project, for a better/easier visual identification

the idea is, since it is becoming multitarget (besides zx-spectrum only), and the essential would be making it targeting the processor itself, and since these processors are from around 70's and 80's, i used a colour palette very used on 70's (and some computers from that time, like from Atari and Commodore uses this palette as well), and the cube as the most used to represent a basic compiler-interpreter, and the simplicity because how simple is to use a tool like zxbasic-compiler - what do you all think?

the final version is this one:

Since z80.py is the essential part of zxbasic-compiler that is used for reference when compiling the resulting .asm into binary, would be a good idea if we start to create similar code for 6502, 6809, 68000, etc., for expanding zxbasic-compiler to other 8bit/16bit platforms? would be this a good start?