Author Topic: Axe Parser (Read 551963 times)

ztrumpet · « **Reply #90 on:** February 18, 2010, 09:01:32 pm »

I'm pretty sure since it's an Asm program, it will run faster (15Mhz) on the 84+/se calcs. Can someone back me up?

Also, the "fast" speed is 15Mhz but what is the slow speed (83/83+). Thanks!

Eeems · « **Reply #91 on:** February 18, 2010, 09:02:47 pm »

well actually apparently the 84+/se needs to be set to 15Mhz for ASM....but I don't know...

DJ Omnimaga · « **Reply #92 on:** February 18, 2010, 09:07:22 pm »

when you play a game like Galaxian or Gemini, the calc is slowed down to 6 MHz when launched. I think some games manages to set the calc to run faster for certain game tasks and even during entire games, though.

Quigibo · « **Reply #93 on:** February 18, 2010, 10:00:28 pm »

The reason for the down internet is that I just moved closer to the college and I haven't gotten the internet service yet.

Games will most likely not be comparable to the size of the source. There are several reasons for that. First of all, many of the routines can be smaller (like Dispgraph) if they use the built-in operating system calls, but that would really defeat the purpose of this project, so I am writing my own faster routines. Secondly, Axe source code can be made more compact than BASIC source code of the same program, so that kind of gives a bias to the file size numbers. Lastly, you have to re-learn how to optimize code. Similar to how there are so many tricks in basic to reduce size and/or increase speed, there are many many more shortcuts in Axe. For instance, A+1 results in smaller code and faster speed than 1+A.

Don't forget, I still have a lot more optimization to do. I've already made a lot of improvements for the next version, its already producing 15% smaller code and there are still many more optimizations to do. Another thing that will be added in the future will be shell support meaning that some routines will simply be calls to the shell functions, greatly reducing the file size. In the future, I would expect well optimized Axe Parser code to be approximately 1-2 times the size of its source, and only about 1.5 times the size of a pure assembly equivalent.

DJ Omnimaga · « **Reply #94 on:** February 19, 2010, 02:15:46 pm »

Oooh ok I see. In my case I still lived at my mom's and she felt I spent too much time online so she got rid of my access, even thought I was the one paying all of it and that I was adult

, don't wonder why I moved out the summer after... (see what it did to Omnimaga from Feb to Jun 07)

I recommend writing your own routines, personally, providing it's not tasks close to impossible (I heard doing an horizontal line routine in ASM can be extremly hard), because ROM Calls are often slower in general than if you do it yourself.

I don't really mind if the compiled programs are the exact same size as the source, though, altough smaller will give more freedom in what we want to create ^^

On a side note: how much RAM is needed to compile a program besides the source RAM + the RAM the compiled program will take?

Quigibo · « **Reply #95 on:** February 19, 2010, 02:52:23 pm »

Well in the future, the source will be archived as it is being compiled. No RAM is used in Axe itself, so you have the entire free ram to create the executable.

By the way, that cave scroller game got reduced by about 50 bytes when I compiled it with the new automatic optimizations, plus I reduced it another 50 bytes from simple optimized source code tricks. An additional 50 bytes or so could be shaved off by using Ion routines. There is even more that can be done, but I'm just demonstrating that the file size you see now will in no way be the final size when I finish this project.

DJ Omnimaga · « **Reply #96 on:** February 19, 2010, 03:03:48 pm »

aaah cool, will it be hard to implement, tho? I heard writing to flash can be quite a challenge, unless for example, the program would be compiled completly in RAM, then archived (which would require more RAM). I could be wrong, though.

Quigibo · « **Reply #97 on:** February 21, 2010, 09:28:25 pm »

New update is here! Expect a new update every Sunday from now on I think.

This version is much more powerful, but still lacks data structure manipulation for complex games (you know, lists and matrices and stuff). But that will be what I'm going to work on next.

I also included a tiny optimization tutorial with some stats.

DJ Omnimaga · « **Reply #98 on:** February 21, 2010, 09:48:33 pm »

Darn that's impressive! Glad you got so much done so far, and that game runs so friggin fast compared to BASIC. Nice job on the project so far ^^, I'm glad finally an alternative BASIC language is going further than just speculation and mockups

jsj795 · « **Reply #99 on:** February 21, 2010, 10:05:18 pm »

WOW! Lovely! I would definitely use this for the TLM sequel if I make one!
I love the screenshot too! They are AWESOME
Goob job, and keep up the great work!

Raylin · « **Reply #100 on:** February 21, 2010, 10:31:01 pm »

Question.
Can xLib commands be parsed as well?

Eeems · « **Reply #101 on:** February 21, 2010, 10:43:58 pm »

No they can't, this isn't anything like standard BASIC, it's got it's own command set.

Quigibo · « **Reply #102 on:** February 22, 2010, 02:51:36 pm »

I've never used xLib, but if there's any commands from there you would like to see in Axe Parser, you can always request them.

Raylin · « **Reply #103 on:** February 22, 2010, 03:36:18 pm »

It would be interesting to see:

*[ON] Break toggle on/off
*Tilemapping
*Text Modes
*Draw Shape (a MUST)
*Celtic III filesystem (the ability to make an AppVar and such.)
*Background Hex Sprite scrolling

ztrumpet · « **Reply #104 on:** February 22, 2010, 03:36:40 pm »

I really like the new commands!
Can we do getKey(101)?
All the new commands are excellent, but I think Horizontal and Vertical are the best.

Oh, and the Optimizing Tricks are excellent.

Author Topic: Axe Parser (Read 551963 times)

ztrumpet

Re: Axe Parser

Eeems

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

Quigibo

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

Quigibo

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

Quigibo

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

jsj795

Re: Axe Parser

Raylin

Re: Axe Parser

Eeems

Re: Axe Parser

Quigibo

Re: Axe Parser

Raylin

Re: Axe Parser

ztrumpet

Re: Axe Parser