Update time!
Okay, with this version, there are some significant updates that will lend to some much needed features and that will help me add new commands.
Bug Fixes:
-Apparently I broke the sprite routines in the last version, but only for the non-hex commands. I fixed it here

Updated Commands:
-Now any variable name inputs aren't limited to named vars. For example, "DStr1" is a valid variable name (to access Str1)
-Fix has another mode for Hexadecimal mode. This makes all numbers get read as hexadecimal.

New Commands:
-Asm(
This lets you use an external, squished ASM program
-IS>(
This will use a pointer var to read variable data. It then increments the pointer var.
-Archive
-Unarchive
-Delvar
-solve(
This is actually going to be a command subset. This has currently 3 commands:
solve(0 is used to copy a var from archive or RAM to a new var
solve(1 is used to copy a piece of RAM to another location (copying forward)
solve(2 is used to copy a piece of RAM to another location (copying backwards)

I don't have any real example programs ready that display the new commands in action, but I can see these new commands as being highly useful. For example, using the IS>( command will make it fairly easy to make a parser. I actually made this because I was working on a drawing program that stored the drawing as shapes and commands as opposed to a bitmap.

I would like to add augment( and sub( to resize variables, too.

I hope this works out well for people! Hopefully I can add new sound and particle effects, sometime
I am also working on the start of an error handler, but I want to make it like a hook. Like, if you do something that will cause an error, it redirects the code to another part of the program for you to handle.

It depends on the kind of math you are working with. It cannot use large numbers (should I add a command for that?), but it can run algorithms quickly and efficiently. For example, when I was studying Number Theory over the summer, I made algorithms using Grammer to compute such things as nCr, gcd(), lcm(), prime testing and whatnot (I have added some of those as commands). I have also made a gravity simulator in Grammer code, so that works nicely and I have made several arbitrary precision algorithms (like for the four functions), and I have made algorithms for finding the square root (rounded or not), drawing a circle or line, sine and cosine, and all sorts of other goodies. A lot of these algorithms turned into actual commands that I rewrote in assembly

So really, it depends on what you need to do The math in Grammer is limited, but it typically returns a lot of info. For example, division returns the rounded down value in Ans which is great for a lot of algorithms and it also returns the remainder in theta prime which is often even better in number theory.

If you have any questions on how to do something, you can post in the Grammer Q&A topic I would love to help with math stuff if I can

Ah, okay I still wonder how fast it will be >.>
An actual command might be more conducive to making background music via an interrupt (I just wanted to use the word conducive )

I still think I should add sound commands, though...

Congradumalations DT!

chattahippie is correct There are some things that can be done much faster with Axe, but Grammer can have a major size advantage over Axe or assembly programs (and even BASIC-- sometimes). Another nice thing is that Grammer programs can be run from Archive (if the Grammer App is installed).

If you check out the Partex 2 example out, that is an example of a program that would probably be a bit large in Axe, but about the same speed Still, Axe has its advantages

As a progress note, I have added the Asm( command, so now Assembly programs can be run from Grammer programs! I am still working on some family health issues though, so I haven't done much and I haven't been on much

Ah, okay. I've only ever used interrupts to toggle two buffers, so I only had something like this as my interrupt:
DispGraphH
DispGraphI
End


Hmm, I'm not actually sure I don't seem to have a problem with having multiple DispGraphs in there (I tried 6) and those are the slowest commands. I will have to test code to see what works and what doesn't...

EDIT: That is a very good question, by the way