Quote from: Runer112 on October 29, 2010, 07:28:20 pm

Code: [Select]

Lbl 22
Return *22

Wow...didn't know you could do that. Thanks!

And also; what if I didn't need the ^r? Would it make a difference?

Yeah, in Axe commands don't need to be directly linked. Evaluating <exp> would put it's value into what you could call the "Ans of Axe" (the hl register), and you can act upon that value whenever you want. It doesn't have to be in a command on the same line, or in this case, even in the same general area of the program.

You can do some pretty crazy stuff using this. The most basic example would be something like this:
0→A→BYou're not actually saying 0→B, but because storing variables doesn't overwrite the "Ans of Axe," the value will remain and can be put in B. If you want to see a more advanced use of this, take this code for example, which I'm using in what I'm working on now:
Vsub(DM3)
...
Lbl DM3
  abs()-{r₁}
ReturnThe absolute value command doesn't even have an argument! But it doesn't care, it will operate on whatever is in "Ans." Entering an expression or value inside the parentheses would be a more logical way to put a value in "Ans" for the command to operate on, but if you don't enter anything there, "Ans" will simply stay as it was before the command was reached (in this case, with the value of V) and the absolute value of that will be calculated.


Also, adding the ^r to subroutine calls bloats the call a fairly large amount. Calling a subroutine always costs a base of 3, but without the ^r modifier, each argument takes 6 bytes, whereas calling a subroutine with the ^r modifier costs 15 bytes for each argument.

On a related but not related note, how large are the Rect(), RectI(), Rect()^r, and RectI()^r routines?

...How big are the sprite routines?

Ok; good. I'm going through all my code checking that my subroutines are actually worth having as subroutines using the 15byte-per-argument ^r. My window drawing routine saves about 393 bytes per call

I'm going to assume it's not worth it to make a routine that just does PtOn(r1,r2,r3) though...right?

Those are the sizes of the subroutines, not the calling routines.  The first time you use Pt-On for instance, it creates the subroutine in the data section.  Then, it calls to that routine.  Each call after that no longer has to recreate that routine anymore and just links to the one that already exists.  The only time you would want to put an Axe call in a subroutine is if you're always using a specific combination of arguments over and over again in the code.

If you want to know the calling overhead, compile "Pt-On(1,2,3):Pt-On(4,5,6)" and subtract that size with "Pt-On(1,2,3)" and that's your calling overhead.

a circle with a negative radius makes weird graphical errors happen, and Abs() should fix it although why is your radius going negative in the first place?

Oh wait do you mean the weird fractal thing that occurs when it is negative? Quigibo posted a screenshot of it somewhere...

EDIT: On an off-topic note, awesome avatar Darl181.

I can't seem to find it. But it looked pretty awesome. I remember a discussion of whether or not to add an absolute value into the command itself...