Well, he's using only one byte at a time anyway, so its perfectly fine and more optimized to just do the 8 bit operation.  You could "or" the screen 2 bytes at a time too, but I'm not sure which way would be faster.

oh good. I can use it then!

Oh, and just to clarify, if you want a fourth buffer, all you have to do is add a Zeros(768)->Name and then reference that name instead of L6/L3/L1 to use that buffer.

I second (third) the stereo sound Axiom request.

If it hasn't been already mentioned, an axiom focused around better graphics support.

Specifically, flood-fill, drawing polygons (not necessarily concave or complex, just convex would probably be adequate), and maybe support for quickly drawing curves (by implementing something like bezier curves, for example).

Although really, just having polygons would be epic.

Ah, you mean not wireframe, but no shading? Even dithering on a side for color isn't too hard. Been done in BBC Basic at least

You can have vectors in Axe simply by storing each component in a separate variable, and doing the dot product by just doing the math yourself X1*Y1+X2*Y2 I use vectors all the time in pretty much every single one of my games, I don't think you need Imaginary numbers in order to use them

In that case, wouldn't a dedicated vector axiom be better than an imaginary number axiom? 

Well they are built in using Floating Point math, did you mean an axiom that gives you floating point accuracy vectors?