Amazing work Quigibo! I can't wait for 0.5.2!

Quote

ERR: BLOCK Either an “End” is missing you you have too many “End”s.

This is from documentation.pdf. What if there is an ERR for too many "End"s and an error for not enough?

That's actually a good idea. One feature request I have is, when Axe encounters an error, it actually keeps going, looking for all the errors, and then lets you go to any of the error. Then, if all of the errors have the same, underlying cause, you can fix it. (This once happened to me in a C# program. I put a closing bracket in the wrong place, yielding hundreds of errors simply because my code was outside of legal programming space.) Also, this would let you have warnings (nonfatal errors such as unclosed parentheses, incorrect arguments in a subroutine, over 8811 bytes of code, and whatnot).

You can only have a certain number of nested conditionals before the parser no longer has enough RAM to keep track of them and is forced to throw an ERR: BLOCK. You can manually make ElseIf analogs that don't use nested conditionals by doing something like the following. They will result in the same compiled code too, so you don't have to worry about the fix bloating your code.

Code: (Uses nested conditionals) [Select] If -1    .Stuff   ElseIf -1    .Stuff   ElseIf -1    .Stuff   ElseIf -1    .Stuff   End

Code: (Doesn't use nested conditionals) [Select] If -1  .Stuff  Goto END End If -1  .Stuff  Goto END End If -1  .Stuff  Goto END End If -1  .Stuff  Goto END End Lbl END

Alternatively, if you're using 3 or more ElseIfs in a row, it's optimal to turn the whole chain into a subroutine, like this:

sub(IF)

Lbl IF
 If -1
  .Stuff
  Return
 End
 If -1
  .Stuff
  Return
 End
 If -1
  .Stuff
  Return
 End
 If -1
  .Stuff
  Return
 End
Return


If you need more than 19, maybe you could find some way to wrap it in a loop instead? Sort of like a switch statement?

doesn't those code examples work anyway? o.O

The second code example you posted already works. But while checking for individual keys or any key is easy, what you suggest is not nearly as easy. This is a good example of the kind of function that could be useful in an Axiom, but isn't really needed enough (especially for its relative complexity compared to other key commands) to warrant making it a built-in feature.

I have two more Ideas:
An option to show the list of variables a program uses
And a Widow command, think of scrolling around a pic that's bigger than your computer screen, something like Window(Pointer to start of data,Width of pic, Highth of pic, x-coordinate of start, y-coordinate of start
Where start is the coordinate in the too-big pic that will be mapped to 0,0
And also Window()^r
And StoreWindow() which would take the same arguments, but put the screen onto the pic instead of the other way around. And, of course, StoreWindow()^r