The thing is, some of the stuff we're talking about here is pretty advanced.  Most programmers won't need to use hexadecimal or multiprecision byte storing, but its pretty cool that you CAN do it.  Hence, Axe Parser has a very wide learning curve.  Its very easy to learn the basics but as you start to get more advanced, you can start doing some pretty crazy stuff.  Even when staying within the syntax and not using assembly, you can literally do almost everything.  Well... maybe not everything right now, but when Axe is finished, this is what I'm hoping.

Yes, it is advanced but at least we are talking in TI-BASIC like syntax which people are familiar and they will focus on comprehend the theory (generally mathematics) behind it.
Trying to learn this along assembly mnemonics and many possible hazards (register destroy, limited instruction set) is so much harder.

I wonder if Axe Parser can really help some people to pass from TI-BASIC to assembly...

I think a nice feature would be something like the Switch statement in C, for when you have a lot of different values to check against (like colliding with a tilemap or handling various different types of objects). It should generate a jump table, and probably be forced to values from 0 to N (if you want A to A+N, just subtract A from the value you are switching).

A vector table would save bytes if it is large enough. Speed is not substantially different.

One alternative is sending Nspire8x by brandonw to a TI-84 and connect with the Nspire. It can send the loader of Ndless (hack it) and at some point send/receive Nspire stuff.

But I don't know how would you send files from the x64 pc...
TI-Connect has a 64-bit patch, why TI didn't do the same with the TI-Nspire Computer Link Software?

This month was quite active too. How do I know how much?
And many new sections. Another great month for Omnimaga.

Macros are like a language that can produce assembly code and ease some tasks (like math tables and other data). See wikipedia topic for better explanation.
SPASM macros can be quite fun (recursing, dynamic including echoed files...).

On the macros itself I have come with these nifty ones:

- var.inc - var allocation
;Example usage:
; varloc(tempswaparea)
;player_x = var(1)
;player_y = var(1)
;buffer_bullets = var(128)
;saveSP = var(2)
; varloc(textshadow,128)
;attack = var(1)
;deffence = var(1)
;overflowedvar = var(500) ;this will give a warning on assembling because overflowed the safe ram (on calculator causes RAM Clear, normally)

#macro var(var.size)
 #define var.counter eval(var.counter+var.inc)
 #define var.inc eval(var.size)
 #ifdef var.end
   #if var.counter>var.end
    .error "Variable allocation overflow!"
   #endif
 #endif
 var.counter
#endmacro

#macro varloc(varloc.value,varloc.size)
 #define var.counter eval(varloc.value)
 #define var.inc 0
 #ifdef varloc.size
   #define var.end eval(varloc.value+varloc.size-1)
 #endif
#endmacro
- convhex.inc convert a label, number, equate or define to hexadecimal representation
;Example usage:
; .echo convhex(%10000000)
;label:
; .echo convhex(label)

#macro zconvhex(hexn)
#if hex_remain == 0
   "$",return
#else
 #define hex_digit eval(hexn & $0F)
 #define hex_remain eval(hexn/16)
 #ifndef return
   #define return ""
 #endif
    #if hex_digit == 0
      #define hex_char "0"
    #endif
    #if hex_digit == 1
      #define hex_char "1"
    #endif
    #if hex_digit == 2
      #define hex_char "2"
    #endif
    #if hex_digit == 3
      #define hex_char "3"
    #endif
    #if hex_digit == 4
      #define hex_char "4"
    #endif
    #if hex_digit == 5
      #define hex_char "5"
    #endif
    #if hex_digit == 6
      #define hex_char "6"
    #endif
    #if hex_digit == 7
      #define hex_char "7"
    #endif
    #if hex_digit == 8
      #define hex_char "8"
    #endif
    #if hex_digit == 9
      #define hex_char "9"
    #endif
    #if hex_digit == 10
      #define hex_char "A"
    #endif
    #if hex_digit == 11
      #define hex_char "B"
    #endif
    #if hex_digit == 12
      #define hex_char "C"
    #endif
    #if hex_digit == 13
      #define hex_char "D"
    #endif
    #if hex_digit == 14
      #define hex_char "E"
    #endif
    #if hex_digit == 15
      #define hex_char "F"
    #endif

 #define return eval(hex_char,return)
 zconvhex(eval(hex_remain))
#endif
#endmacro

;wrap the main macro up with another macro to clear the global defines to work more times
#macro convhex(zn)
  #define hex_remain -1
  #define return ""
  zconvhex(zn)
#endmacro
- breakpoint.inc, this echo to a text file named breakpoints.txt the address of breakpoints
(you need convhex macro)
;breakpoints.inc
;by Galandros

#include "convhex.inc"
#macro BREAKPOINT
 #ifndef BREAK_F
  .echo > breakpoints.txt "\nBreakpoints:\n"
  .echo >> breakpoints.txt convhex($),"\n"
  #define BREAK_F
 #else
  .echo >> breakpoints.txt convhex($),"\n"
 #endif
#endmacro

;Alternatives to break macro name
#define breakpoint() BREAKPOINT
#define .breakpoint BREAKPOINT
- relocation
(this was not made by me, actually)
#macro relocate(location)
 #ifdef g_old_location
   .error "You cannot nest relocate blocks!"
 #else
   #define g_old_location eval($)
   #define g_new_location eval(location)
   .org location
 #endif
#endmacro

#macro endrelocate()
 #ifdef g_new_location
   .org $ - g_new_location + g_old_location
   #undefine g_new_location
   #undefine g_old_location
 #else
   .error "No relocate statements corresponds to this endrelocate!"
 #endif
#endmacro

How to use:
1. copy the text to some text file using Notepad, for example.
2. include in the source code with #include macro.inc directive
3. call it within the source code

Notes:
- to see the examples uncomment the lines (simply delete the ";")
- only works on SPASM. I could try TASM compatibility, but meh, SPASM has some many reasons to be used
- I am giving a cookie especially for Eeems. You can use this macros in the ADE. Just give me credit and put in the include file that the macros were given by me (Galandros). You can include in your IDE, just do the same as I wrote before in this line.

More macros will come. I have done convbin (convert equates to binary)
I am going to release a pack of SPASM macros.
You can post your macros, too. Or request macros. I am doing some experiments with SPASM macros because you can do pretty much everything.

You are spamming here! -7 points to each one! j/k

When is the assembly routines section going to be created?
I have some routines (with bits of tricky optimization) to show and see optimizations.

I do also have formidable SPASM macros.