Quote from: Aichi on November 05, 2010, 02:23:47 pm

It seems like DCS7 doesnt support descriptions when I compile an axe code to an Ion prog.

Doors definitely supports Ion descriptions... Do you have another shell you could try it in?

Ah I see. So this is definitively an issue on Axe's side.

Using Pause without an argument likely uses the last answer as the argument. It may have "crashed" because you had a very large number there (or 0).

So, I think I have come up with a foolproof method for checking whether interrupts are enabled, even if an interrupt occurs at an inopportune moment:
;Push a zero byte to the stack and pop it
xor a
push af
pop af
ld a,i
jp pe,interrupts_on
;See if an interrupt triggered. If so, the byte on the stack will not be 0 anymore
;unless this code is executing from $0000-$00FF area, which would only happen if you are writing an OS
dec sp
dec sp
pop af
or a
jr z,interrupts_off
;If interrupts were on, set A to $FF so the increase will set parity even
ld a,$FF
interrupts_off:
;Set parity odd
inc a
interrupts_on:
Edit:
My code had a logical error, it should be fixed now

Not sure if this has been mentioned already, but if you overwrite an external variable that's been in archive, it just gets deleted and not overwritten.

When I've done that it just becomes hidden and archived.

So, I think I have come up with a foolproof method for checking whether interrupts are enabled, even if an interrupt occurs at an inopportune moment:

Awesome!  Is this any slower than the routine currently being used?

The signed division auto optimizations are gone

EDIT: Also, sprite routines targeted to arbitrary buffers reverse the x and y arguments.

EDIT 2: Oh, and in the commands list you accidentally call EXP1**EXP2 signed multiplication instead of fixed point multiplication.

I think I saw this reported elsewhere by another person, but I forgot which thread. Seems like a bad bug X.x

Quote from: Runer112 on November 10, 2010, 05:24:48 pm

EDIT 2: Oh, and in the commands list you accidentally call EXP1**EXP2 signed multiplication instead of fixed point multiplication.

It actually is a signed fixed-point multiplication. The list doesn't say "fixed-point" in so many words, though it does describe the type of number it is.

You're right, there's definitely some signed stuff going on here. But it's a good thing you pointed this out, because now that I look into it more, it appears that the routine itself is buggy. For instance, ᴇ0400**ᴇ2000 evaluates to ᴇ8000, although I believe it should be ᴇ0000 signed. It seems to be a problem with signed overflows not carrying properly. As another example, ᴇ0410**ᴇ2000 evaluates to ᴇ7E00, although I believe it should be ᴇ0200.

Can someone please verify that this is a problem? Or tell me how I'm misunderstanding it and why it's not a problem?