When I say {L1+200+A}, is L1+200 calculated when parsing or when executing ?

Axe calculates it when compiling. (You can optimize it more as {A+L1+200}, by the way. Always put constants after.)

Ok thanks
(and for putting constants after, I do it for little pieces of code like A+3→A but I always forget it otherwise -.-°)

aeTIos:
What is the "and" equivalent of ^2 then ?

and 1 pretty much is the equivalent of ^2; and 2 just doesn't set the high byte to 0, and is thus 2 bytes smaller and 7 cycles faster. Or you could use the full 16-bit bitwise AND, ·1, which results in the exact same compiled code as ^2.

There is sub(LBL,arg) and sub(LBL^r,arg).
There is LBL(arg). But is LBL^r(arg) valid ??

I would imagine that LBL(args)^r doesn't exist because parsing that would require look-ahead parsing to detect the ^r before the arguments are parsed, but LBL^r(args) seems like it could be implemented. Not sure why it isn't yet.

How much space does calling "stdDev(PTR,N)" take ??
How much space does calling "sub(LBL^r,arg)" take ??

Excluding PTR and N of course, the stdDev(PTR,N) call takes 4 bytes, plus 14 bytes for the routine itself.
Again excluding the arguments, sub(LBL^r,args) takes a pretty substantial 12 bytes per argument, plus 3 bytes for the call. Unless you absolutely must have a recursive function, I suggest avoiding this, as this costs an extra 9 bytes per argument.

Twice (or as often you use it). To prevent that, you can do
"text"->str1
...
text(0,0,str1)
...
text(0,6,str1)


(double posting after a little while)

How do we end a conditionnal comment ? with "..." or "...End", like

this	or this
...If CST	...If CST
code	code
...End	...

?

What's the sense of using comment ifs?
I mean, you could just make it normal, I don't think it compiles different on other calcs....

If °CONST=83, Code1 is compiled, else Code2.

Code: [Select]

:83->°CONST
:
:...If °CONST=83
:.Code1
:...Else
:.Code2
:...End

If you tried to compile that, Axe would throw an error. There is no End to end conditional comments, you just end blocks like you would end any conditional comment:

:...If CONSTANT_EXPRESSION
:.Code goes here
:...Else
:.Other code goes here
:...


---

What's the sense of using comment ifs?
I mean, you could just make it normal, I don't think it compiles different on other calcs....

You are correct that the code doesn't compile differently on different calculator models on its own. But you can make it compile differently by changing the value of a constant, allowing you to quickly and easily change what code is compiled. This is useful for Axe libraries, creating multiple compiled variations of your program, and testing your programs, among other things. For instance, you could put blocks like this in your program:

...If °DEBUG
ClrHome
Disp A►Dec,i,B►Dec,i,C►Dec
getKeyʳ
...

And then simply change the value of the constant °DEBUG before compiling to allow you to turn debugging output on and off. The advantage over a normal If statement is that, if °DEBUG equals 0, the debugging code is not included in the compiled program, which is good if you have 500 bytes of debugging code and you don't want it bloating your official program release.

Oops, I wasn't correctly remembering my previous experience with conditional comments. Yes, ...Else works. What had me confused is that I remembered ...ElseIf not working and I must have grouped the two together in my mind.