Now we have sub-forums for Help&Support and Documentation. That makes things tidier, especially with a growing forum.

I think this original top-level forum I'm posting into creates a kind of ambiguity, it's not clear what its purpose is any more.

I suggest to use it only for announcing new releases, or general announcements of the developer. Maybe it could be a read-only sub-forum for the users? The rest of the current messages would be moved into the proprer sub-forums.

More: This top-level forum itself could be moved into a new "Release announcements" or "Developer announcements" sub-forum, so the sub-forums list would be plain clear: no doubt where to post.

Just for your consideration.

I suggest to use the FreeBASIC docs as a guide, especially the FreeBASIC Table of Contents. What do you think?

By the way, I see a problem about FreeBASIC wiki: it lacks page hierarchy, it doesn't show a breadcrumb on the top, what is very important to see where we are in the page tree. Many wikis lack that feature. Some of them use the raw page name (e.g. "main.reference.functions" would be a deeper level than "main.reference"); others use page metadata to configure the hierarchy (what is more flexible because page names can change without changing the structure).

Another possible model is the PHP documentation (see an example of PHP doc page): description, parameters, return values, examples, see also, user contributions...

Boriel,

I am willing to help with the wiki version of documentation. Actually, I think I've probably put edits into half of it *chuckle*; including starting a "library" section and listing things like Fsin, Fsqrt and iSqrt. I think that it's possible to work out the Sinclair Basic compatible statements, but anything not compatible needs to be documented more fully. So let's start with that.

1> Are there any words that are NOT already in the reserved word list - <!-- m --><a class="postlink" href="http://www.boriel.com/wiki/en/index.php/ZX_BASIC:Identifier#Reserved_Identifiers">http://www.boriel.com/wiki/en/index.php ... dentifiers</a><!-- m --> that we should know about?

2> Are there any extensions to the language, such as with PEEK and OVER that we don't have documented there?

Here you are my first two cents for the wishing well:

Now the DO-LOOP syntax is:

Quote:Do
[ statement block ]
Loop [ { Until | While } condition ]

Quote:Do [ { Until | While } condition ]
[ statement block ]
Loop

I ported some old code I developed with the aid of a couple of snippets published in Microhobby and some documentation for the AY chip to ZX Basic. The original was plain interpreted Sinclair BASIC. It may be useful to create simple sound effects, but nothing very fancy. Porting WYZ's replayer would be a better idea, but I have no time at the moment.

Try this:

This is a new beta version (released a minute ago :!. Basically it adds 3 new command line parameters:

• --strict-boolean will enforce boolean results to be always 0 or 1 (with a slight impact on performance). Using --sinclair also enables this feature.
  
• --debug-array will raise an error if an array access is made out of boundaries (3 Subscript Wrong)
  
• --debug-memory will raise an error when out of memory. This might happen when working with strings

I have a program (fourspriter. Yet again!) that has a compilation error "no such label". Except I can see it. Right there! :-)

Am I going crazy?

I copied and pasted the following code into a separate project:

Sometimes, in order to use the Spanish characters (áéíóúüñÁÉÍÓÚÜÑ¿¡) in my Spectrum programs, I put them in the place of less used Spectrum chars (#, ', @...).

In the source code of my current project there's a lot of Spanish texts to be printed by the Spectrum. It would be uncomfortable to use those fake chars all over the source. Then I had a quite brilliant idea: Let's use the same standard character set both in the source code and in the Spectrum!

First, I wrote a trivial asm sub to change the character set address. Then I added the character graphics, with the Spanish chars in the right position (in the ISO-8859-1 standard). The only needed trick is to fill the gaps of the unused chars. Happily, I already had all the character definitions is assembler DEFBs, in another project of mine.

This is the first part of the sub:

Some times I need to check the assembler, and I have to compile the sources twice in order to get also the .TAP file, because anyway I need to execute the program too.

Maybe in the future both the assembler file and the object file could be created with one single command?

I realized that some comparations with string lenghts return different values than in Sinclar Basic: