Sorry to be creating so many posts the last couple of days.

Should this work?

Not sure if this is a bug or not, so I thought I'd pose the question first.

I read this post from last year, which suggests that @ addresses should now be treated as constants:
<!-- l --><a class="postlink-local" href="http://www.boriel.com/forum/post4283.html?hilit=%20not%20constant%20#p4283">post4283.html?hilit=%20not%20constant%20#p4283</a><!-- l -->

So I figured I should probably be able to make some labels and then do something like this:

Okay, I think I figured out what my other problem is.

In 1.3 I could call a function in the code before it was declared providing I declared the function with a prototype at the top of the class. So this would've worked okay, despite the 'addWibble' function appearing after the call to 'addWibble':

Hi guys, it's been a little while.

I finally got around to upgrading to 1.4.0-s1881 and set about recompiling a bunch of old stuff to see how it turned out. One thing I'm having a problem with is that some of my code uses consts in the declaration of arrays, which was fine in 1.3 but doesn't seem to like compiling in 1.4.

e.g.

Something like this:

<!-- m --><a class="postlink" href="http://virtualink.wikidot.com/fbex20">http://virtualink.wikidot.com/fbex20</a><!-- m -->

Hello.

I got a program that works fine under 130s1121 but not under 140s1876. When I try to compile it then it bombs with this message:
Traceback (most recent call last):
File "/home/pi/zxbasic/zxb.py", line 348, in <module>
sys.exit(main(sys.argv)) # Exit
File "/home/pi/zxbasic/zxb.py", line 274, in main
translator.visit(zxbparser.ast)
File "/home/pi/zxbasic/ast_/ast.py", line 105, in visit
stack.append(self._visit(stack.pop()))
File "/home/pi/zxbasic/arch/zx48k/translator.py", line 143, in _visit
return NodeVisitor._visit(self, node)
File "/home/pi/zxbasic/ast_/ast.py", line 118, in _visit
return meth(node)
File "/home/pi/zxbasic/ast_/ast.py", line 122, in generic_visit
raise RuntimeError("No {}() method defined".format('visit_' + node.token))
RuntimeError: No visit_SAVE() method defined
Usage: zxbasm.py <input file> [options]

I do not wnat to share the source on a forum, is there any way that I can get the source to you Boriel so that you can have a look at it?
Also, under the old version if you had a wihite paper and a black ink but a yellow border then the SAVE command did change the paper color to yellow afterwards and the tape message got displayed in paper yellow instead of white. Highly fishy. And if I tried to compile this program with -O3 then it bombed so I had to set it back to -O1. Now it totally refuses to compile under the new version. Help would be good here Boriel.

Mi wish is easy to satisfy: I need one label after CP 80h in <print.asm>:

I've never programmed used bank switching, but now I'm developing a new external interface to convert a 16Kb Spectrum to a machine very close to a plus 3 machine but with 512Kb of RAM, and due to it, I'm starting to be interested of this kind of programming.

I know now that ZXBasic has not support for bank-switching.

I have a suggestion about the possibility of support it natively and then support 512Kb of RAM too. The method to change the page above 128Kb is the same that the used in Pentagon, ie using bits 6 and 7 of the same port than 128Kb ($7FFD).

Could be very interesting to do it, because if we do it manually we can only use it for data, as a very fast disk, but not for code. The best way is to implement it natively. It is not possible to do that with a library.

The main challenge could be to use the same addresses for different functions.

I've never programmed used bank switching, but now I'm developing a new external interface to convert a 16Kb Spectrum to a machine very close to a plus 3 machine but with 512Kb of RAM, and due to it, I'm starting to be interested of this kind of programming.

Have ZXBasic support for bank-switching?. If the aswer is yes, I have a suggestion about the possibility of support for 512Kb of RAM. The method to change the page above 128Kb is the same that the used in Pentagon, ie using bits 6 and 7 of the same port than 128Kb ($7FFD).

If it is not supported, could be very interesting to do it, because if we do it manually we can only use it for data, but not for code. The best way is to implement it natively. It is not possible to do that with a library.

The main challenge could be to use the same addresses for different functions.

I think POKE STRING would be useful in many situations. It would poke the content of a string (not its lenght). I've written it this way: