How different is AXE math from BASIC math?

Axe numbers use 2 bytes to represent an integer from 0 to 65535.  Using different methods, you can modify this range to be from -32768 to 32768, still integer.  And then using a method called fixed-point-arithmatic, you can store numbers from -256 to 256, but with accuracy past the basic integer.  In hex, your Fixed point number would look like ##.##, where the ##'s represent the individual bytes.  The advantages of Axe math is that they are extremely fast, as well as being directly integrated with all of the Axe functions.  The disadvantages of Axe math is that they have limited accuracy, and don't work as well in cases where extremely high accuracy is needed.

Basic math (in regards to using it in Axe) is extremely limited simply because Axe only supports importing and exporting Basic variables as integers.  Additionally, Axe does not support doing mathematical operations on Basic variables, and lots of Hex code would need to be used to either access the arithmetical BCALLS, or run a Basic program.  Additionally, basic math is much slower than Axe math, because the code is not compiled, and instead is being manipulated by the (inherently) slow BCALLS.  The advantage Basic math has is it's high accuracy, from -1*10^99 to 1*10^99, with a decimal accuracy of 14 decimal places.  Little of this is accessible to an Axe program however, since Axe only supports the integer side of Basic math.

In short, I highly recommend that if you plan to make this an Axe program, you learn how to use Axe fixed point math, as it's not really worth it to jump through hoops simply to use the slower Basic version for a small gain in accuracy.

Yay moving platforms Do they move up and down or side to side?

My program menu is always clean, but I have many many groups, each with many programs inside them, so I have a pretty full calculator

First off, are you aware that Axe has it's own Byte transfer routines?  They have very good features and are very reliable.  Or are you just perusing this topic for the fun of it?  In any case, it may be worthy to note some of the subtleties of how Port command works (or at least what I believe, I am no expert).  If one calculator writes a 3 into the Port (setting both bits), no matter what the other calculator sets the Port to, the Port will still remain at 3.  This is because when a single bit is 'pulled high' (set to 1) on either calculator, it is perceived by both to be high, even if the second calc has it set to be low.  In this sense, if both calculators set the Port to be a certain number, the actual reading of this Port will be the OR of these two numbers.

would you mind posting the specific programs that give the errors, as well as the source programs so we can try this ourselves?  That would help a lot

I assume this is for line clipping?  I have to think there must be a better way to do this Not to mention Axe's default line drawing routine won't work on a buffer that is wider than 12 bytes.

Indeed, Zedd makes moving platforms significantly easier than normal ^^