Quote from: Freyaday on December 15, 2012, 02:10:42 am

Why would you ever have any reason to include the same program twice?

So you'll never include the same program twice, so the fact that Axe lets you include the same program twice is not a problem.
So I really don't get where is your problem

Um, what?
Hayleia, the point I was trying to make with that statement was that there would be no reason to include the same code twice in a program.
Builderboy showed me a possible use for it, though, so I'm dropping it.

I would recommend narrowing down the problem, as it's kind of difficult without learning all of your code to figure out what is going on, and the cause of the mistake is not immediately obvious.  What is the behavior in earlier versions of Axe? 

Freyaday, this behavior is not the result of an Axe bug. This is a result of your use of the parametric variables, which changed with Axe 1.2.0. I think I recommended not using them as general-purpose variables a while before 1.2.0 was released, by the way.

I've got two three.
Trying to make a program with a name that contains invalid characters (like lowercase letters) will sometimes flat-out not create a program instead of cutting off the name.
The error message for a too-large app is "ERR:MEMORY". It really should be something more descriptive, like say, "ERR:TOO BIG FOR ONE PAGE" or something.
Also, sometimes, when you compile something, a full progress bar (just the bar, not the thing around it) will appear on the screen for a split second before compiling begins.

OK, so I don't know if this is a bug or needs to be a feature request. But the following code, which _should_ replace 2 bytes(according to my understanding of the axe syntax). But, I have two issues with the program. One is in the post about the string thing. Anyway, I'll be posting example code to do it along with the dump from the error screen for you.

First one.

:.RC2
:"SILLY STRING"→Str1
:length(Str1)→L
:Disp L►Frac
:det(L)→S
:det(L)→C
:0→T
:L-1→M
:For(A,0,M)
:InData({Str1+A},T)→D
:If D≠0
:.This line right here is the problem...
:.It Also happens at the ^r character, which makes no sense to me.
:{C+D}{^r}++→{C+D){^r}
:End
:Else
:{Str1+A}→{S+A}
:0→{C}{^r}
:End
:End
:length(S)→L
:L-1→M
:For(A,0,M)
:Disp {S+A}►Frac
:Disp i,{C+A}{^r}►Dec
:End
It says "invalid token", even though as far as I can tell it should be _completely_ valid in Axe. I've not seen anything saying I can't replace two bytes in ram, as that whole ^r, thing I thought should've fixed it. Anyway below is a screenshot with the data, as I'm way too lazy to make sure I don't accidently type something wrong and it end up being an _entirely_ different thing going on. If you're not able to modify 2 bytes of data at an address in Axe/that shouldn't be allowed to happen anyway in this syntax. I'll go post in the feature request area about it.



P.S. I looked over the code again, and it seems like it _should_ be valid. Maybe I'm just being really stupid...

Edit 1: I tried moving it down a line, and for _whatever_ reason Axe _hates_ and I mean _hates_ having that all on one line, it seems to work now. Just had to put it on two lines, don't know if that still counts as a bug report or not at the moment.

It's also worthy to note that the ++ operation already stores the incremented value back to where it was read from, so the →{C+D}r part is completely unnecessary (and may not even work 100% of the time, since ++ doesn't always return the incremented value)

I believe that is SourceCoder syntax, in which the radian r symbol is represented as {^r}

OK ...
all I reported seems to be fixed
after looking at asm through my secret exA project, I saw that [H/V]Line(arg,arg,arg) called CD0100 , and 0001 is a space with random code
routine call for HLine(16,,) : 211000E5E5CD(XXXX) ► double E5 causes stack overflow/corruption because of no double D1 to match it ...
and for circle after analyzing it I guessed that some pixels was inverted twice.

Another bug, on a simple program compilation (1st pass, I think) :
UNKNOWN ERROR
long freeze, like a lots of getKey^r (2nd and Alpha worked, but ...)
after a long time (time to found pen and paper) there was the normal blinking indicator after prgmNAME, I pressed [ON]►shutdown►RAM Cleared.
prgm had GetCalc(Y1), Copy(Y1,, ... and nothing else especially.