Well I was thinking of instead of having just "Break" and "Continue", I also have "BreakIf" and "ContinueIf" as well as their conjugates since then they can be used in conditionals because I think that feature would be nice and this way the assembly is more optimized anyway than having a separate conditional.  Also, I'm not even sure how I could make it break out of multiple levels of nested statements anyway with the way I currently handle nested blocks.

My switch command is going to be really different as well.  I need it to be optimized enough where it is much more favorable to use so I think there will be no switch statement, only case statements.  For instance:

:
:A*12+(B/8)         .The last expression used becomes the switch statement automatically
:Case 0
:  .Function1
:Case 83
:  .Function2
:Case -1
:  .Function3
:End
:

The look-ahead parsing to pregenerate a jump table would be messy and memory hungry so I'd have to see how feasible it is.  So that means I am still unsure if automatic breaks would need to be implemented or not.  I'm also unsure if I want to make this command a single byte only command since it could lead to a huge optimization

The "Default" could be written like "Case ?" or perhaps "Else"?

See the TI-Basic code below:

Code: [Select]

"HELLO"->Str1
Str1+" WORLD"->Str1
Can this be done in Axe? How?


And, as for the Bitmap( command, it says the structure pointed to should be width x height x rows of img. What does this mean exactly? Let's say I wanted a blank sprite that is 7x7 pixels. How should my arguments for Bitmap look (The X and Y can be an arbitrary X and Y)?

Here's a way to do what you said, I think. Note that extra data bytes are inserted after Str1 is defined. This is important! Otherwise the new data at Str1 would overflow into other data.

.Data initialization
"HELLO"->Str1
Zeros(6)
" WORLD"->Str2

.Code to append Str2 to Str1
.Copies length(Str2)+1 bytes to include null terminator
Copy(Str2,length(Str1)+Str1,length(Str2)+1)
Edit:
I also have a feature request. A function for _Insertmem and _Delmem (with a warning to use wisely )

Here's a way to do what you said, I think. Note that extra data bytes are inserted after Str1 is defined. This is important! Otherwise the new data at Str1 would overflow into other data.

Code: [Select]

.Data initialization
"HELLO"->Str1
Zeros(6)
" WORLD"->Str2

.Code to append Str2 to Str1
.Copies length(Str2)+1 bytes to include null terminator
Copy(Str2,length(Str1)+Str1,length(Str2)+1)

So, that takes Str1 and adds it to Str2? Writing it into my calculator with a Disp Str2 doesn't return "Hello World"

I also have a feature request. A function for _Insertmem and _Delmem (with a warning to use wisely )

To insert stuff at a memory address and offsetting some of the stuff below, right?

That code should work.  Are you sure you recompiled it after making changes to the source?

The InsertMen and DeleteMem commands I was considering to add at one time, but then I realized that you can do basically the exact same thing by creating an appvar, string, program, etc. in ram and then delete it when you're done to get a quick temporary variable without any extra syntax.

By the way, I happened to stumble upon an undocumented bcall on brandonw's website that is nearly identical to BASIC's "Input" function, and so I've added that functionality now.  The way it works is that it stores the input to a temporary string in ram and returns the pointer to it just like you would read any other external string.  The only difficulty is that similar to strings, its token based instead of character based so anything that's not a number or uppercase letter has to be converted.

The InsertMen and DeleteMem commands I was considering to add at one time, but then I realized that you can do basically the exact same thing by creating an appvar, string, program, etc. in ram and then delete it when you're done to get a quick temporary variable without any extra syntax.

Yes but working at a fixed address would be faster, and I'm all for more speed.