Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 287
» Latest member: _glPl
» Forum threads: 997
» Forum posts: 6,125
Full Statistics
|
Online Users |
There are currently 86 online users. » 0 Member(s) | 85 Guest(s) Google
|
Latest Threads |
мешки для мусора
Forum: ZX Basic Compiler
Last Post: _egKl
Yesterday, 02:15 PM
» Replies: 0
» Views: 1
|
Error: STRING CONSTant
Forum: Bug Reports
Last Post: boriel
06-04-2023, 10:52 AM
» Replies: 1
» Views: 26
|
Pascalated ZX BASIC Demo ...
Forum: Gallery
Last Post: zarsoft
06-03-2023, 11:31 AM
» Replies: 0
» Views: 7
|
Compiles OK then crashed
Forum: Bug Reports
Last Post: Neo-Rio
05-30-2023, 11:11 AM
» Replies: 2
» Views: 57
|
Pascalated ZX BASIC Demo ...
Forum: Gallery
Last Post: zarsoft
05-21-2023, 01:07 PM
» Replies: 0
» Views: 41
|
Pascalated ZX BASIC Demo ...
Forum: Gallery
Last Post: zarsoft
05-15-2023, 02:21 PM
» Replies: 0
» Views: 66
|
Pascalated ZX BASIC Demo ...
Forum: Gallery
Last Post: zarsoft
05-06-2023, 07:56 PM
» Replies: 0
» Views: 60
|
No more loading messages ...
Forum: Help & Support
Last Post: zarsoft
05-06-2023, 10:00 AM
» Replies: 2
» Views: 116
|
Pascalated ZX BASIC Demo ...
Forum: Gallery
Last Post: zarsoft
04-29-2023, 04:33 PM
» Replies: 0
» Views: 69
|
Pascalated ZX BASIC Demo ...
Forum: Gallery
Last Post: zarsoft
04-23-2023, 05:37 PM
» Replies: 0
» Views: 66
|
|
|
Features breaking compilation in older ZXBasic programs |
Posted by: MrKOSMOS - 06-17-2022, 06:51 AM - Forum: Core
- Replies (1)
|
 |
Hello
So I've been using ZXBasic for a while, and after struggling for a while trying to compile some code finally realised some issues. To sum it up, I tried compiling Souls Remastered, since the keyboard input wasn't working on my Timex TC2048. However, while trying to compile I kept getting IF statement errors, which I attributed to the compiler itself. However, it turned out to be due to comments placed in front of the IFs, which were being recognized as one-line commands and "resolving" the IFs, creating errors with the END IFs afterwards. This seems to date back to a previous version before the one-line IF feature was implemented. In fact, many other ZXBasic games by Retrobytes and even the BerkzMan game from the tutorials page seem to expect this feature to be absent in order to compile, so providing a solution seems like a must.
So what do I propose? Well, I see two solutions: One, adding a legacy option for the compiler, say -L. This would be the easiest, and allow compilation of unmodified older code.
Two: implementing a routine that counts all IFs and END IFs in the program flow and checks if they are the same, as well as checking for comments in front of IFs. This may be a more robust solution, letting everyone program as they want without having to check some obscure command line option.
Aside from that, there seem to be a few other bugs. There seems to be no check for writing to memory above the 64k limit, since I have written a few programs that, when loaded through the BASIC loader, give an Out Of Memory error on the Spectrum. Other than that, there seems to be a bunch of data added along the print command, which I assume is a character set. But is this really necessary when the program only uses UDGs or spaces? In that case, the whole set could be left out, saving a decent amount of space. It could even be optionally left out, and swapped for the ROM character set.
Well that would be all, please say what you think
|
|
|
The Disputed Territories of Ghotto |
Posted by: Jbizzel - 03-21-2022, 05:29 PM - Forum: Gallery
- No Replies
|
 |
I made a new game
2 pixel scrolling city bomber type game, with a story built in.
Please let me know what you think.
Credits:
zx basic,
putChar
zx0
zx paint
beepfx
beepola
DamienG fonts
get it here
|
|
|
The sound effect thread |
Posted by: worcestersource - 02-19-2022, 12:03 AM - Forum: How-To & Tutorials
- Replies (3)
|
 |
Hello everyone,
I thought this would be a nifty place to pop some routines to make sound effects without resorting to asm.
Code: sub soundBwop()
dim x, y as uByte
do until x = 255
out 254, (y * 8)
let y = x
do until y > 239
let y = y + 16
loop
let x = x + 1
loop
end sub
Which makes a nice 'bwop' sound. it'll also change your border colour, so add the border value to the out statement to stop it changing colour. For example, for the a blue border:
Code: out 254, (y * 8) + 1
You can play around with this, such as changing the 16 for an 8, or making y count down so the loop duration gets longer each time.
Steve
|
|
|
Testing a variable within a range |
Posted by: worcestersource - 01-27-2022, 08:14 PM - Forum: Help & Support
- Replies (11)
|
 |
Hello!
I was wondering if there was a better way of testing whether a variable was within a range.
So instead of:
Code: IF a > 0 and a < 30 then...
There was a neater and/or more memory efficient method? These sorts of tricks that can help us eke out every last drop out of zxbasic. 
Cheers,
Steve
|
|
|
|