Yeah, the doc probably has some errors, I rushed through it.  What did you find exactly?  Grammar error?  Spelling?  Broken source snippets?  Hopefully not misinformation...

Axe Parser
Beta 0.2.0

---

New Features:

• A real documentation!
• New user interface.
• Compile for shells.
• Contrast adjustment.
• Absorb "Pic" files into programs.

Changed:

• Headers are mandatory.
• Only Axe Source programs show up on compile list.
• Fixed a few more bugs.

New example file from tutorial.

Quote from: Quigibo on April 18, 2010, 12:27:19 pm

the tutorial already assumes you know BASIC

^sounds like you already wrote a tutorial
Would you still like me to write a tutorial/sample program article like you asked before?

I was about to, but I haven't actually yet.  If you think you can finish it soon today, then go ahead, if not, I'll be able to handle it.

Hmm... I don't know.  Is that an option you would like?  I think generally, you won't notice the slowdowns unless you use the same routine over and over for practically the entire program (Like my Game Of Life example).

You're talking to a perfectionist here  But not necessarily next release, I can always tweak it more later, as long as the final version is perfect gray.

Also, I forgot to mention, the only routines I was able to outsource to the shells so far were all the pixel routines.  They certainly cut down on the program size!  But unfortunately, the shell calls are slower becasue they are not as optimized as the routines I'm using.  Its a small difference, but definitely noticeable in the Game of Life  program.  There's nothing I can do about that though...

I've already fixed the DispGraph command.  But I might have to fix it more.  It looks fine in 6MHz mode, but its pretty grainy in 15MHz mode.  If I change the pause times, the opposite happens...  I might have to make it adjust dynamically so both cases look good.

No.  In fact the variables A-Z really are memory locations located between {L1-52} and {L1-2} or something like that I think.  It just does all the behind the scenes work for you when you use the letters.

However, even though they should be as fast, they won't be just becasue I haven't done the hardcore precompile optimizations yet and probably won't for a long time.  I doubt you'll notice the difference though, it just means that when you do {L1+12} like you say, it adds the 12 during execution.  Arithmetic is super fast though, so don't worry about it.

By the way, I'm thinking of adding a new unsigned division routine for division of constants less than 256.  It would be almost twice as fast and twice as small as regular division.  The drawback is that now you'll be calling 2 separate subroutines for long division (division by variables and constants greater than 256) and short division (by constants less than 256).   If you have to use both in the same program, we're only talking about 15 extra bytes total so its worth it in my opinion.

Has anyone used BBC Basic?  I'm doing a comparison between the languages.  What is it usually used for?  Same with xLib/Celtic.  Are they normally targeted for game development or do most people use them for other things.