JustCause, excellently put. Most languages have advantages and disadvantages to other languages and so the programmer picks the most appropriate tool for the task

>.< I saw the post by merth on cemetech and I agree with him.

How is that different from any other language and library? I do a lot of programming in C#, does that mean that the only person who really did any work was the language designers and library writers? Obviously not. If there's a higher level language that exists and makes development faster and easier, I don't see any reason not to use it. Should people learn ASM? Yes. Should they have to stick to it then? No. Should it matter to anyone else what language someone else prefers to write their software in? No--as long as the language isn't getting in the way (or you have to support the code).

Hi These are for you:

And I cannot help you with that, sorry

Welcome home!
Err, *here* >.>

I don't speak a good english but I can understand your message.

Cool, do you speak another language better, then?

Thanks! And hooray for updates

I am not sure that would speed things up too  much just because of how Grammer works. Grammer treats pixel testing as reading from an array as it is, but that could still be useful... Thanks!

Okay, I am not too clear on the last part, but saving the coordinates to an Appvar I can do:
.0:Return
Send(4,"UCoord→V
{V→X
{V+2→Y
Repeat A=15
iPart(V,X
iPart(V+2,Y
Line(X,Y,6,6,2
DispGraph
Line(X,Y,6,6,2
Repeat A
getKey→A
End
X+A=3
-A=2
-A=5
+A=6
-A=7
+A=8
If >90
X
→X
Y+A=5
+A=6
-A=7
-A=8
-A=4
+A=1
If >58
Y
→Y
End
Stop
That will move a rectangle around the screen saving the coordinates to the appvar Coord. To be honest, though, you only need two bytes for the coordinates here >.>

Erm, I accidentally posted the update in the regular Grammer topic, so I am pretty much copying and pasting

---

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.

Grammer 2.10.11.11