How do you do collision detection with sprites in Axe?

How do you do collision detection with sprites in Axe?

To detect if two 8x8 sprites are colliding, simple do

If abs(X1-X2)<8 && (abs(Y1-Y2)<8

I'm sure it could be optimized, but its just a demonstration

Can someone explain what and, or, and xor do in axe?
Not in If statements, but otherwise.  It's not very descriptive in the commands list

By the way, I think a few people have gotten confused a bit. This is not the general Axe Q&A thread, this is just a thread that Scout started to ask a few specific questions for his program. If you want to ask short questions, in the future it would probably be better to ask them in the general Axe Q&A thread made for this purpose.

Can someone explain what and, or, and xor do in axe?
Not in If statements, but otherwise.  It's not very descriptive in the commands list

I think Wikipedia can explain the bitwise operations better than I can. The examples they give are for 4-bit numbers, whereas Axe uses 16-bit numbers. The and, or, xor, and not() commands only operate on the low 8 bits (the high 8 bits will simply be copied from one of the arguments). The ·, ?, ?, and not()^r commands perform the operation on the full 16 bits.

Runer, I'm afraid I'm not very comfortable with the Axe Q&A topic, since a lot of people are asking questions in the same thread :S

I have one more question:

3. How to get arguments in a label that is a subroutine. I want to call it like sub(DW,"HEY",1 and in the Lbl DW I want to get the arguments. Thanks.

r1 is the first argument, r2 is the second, etc. They're all accessed from VARS > Y-VARS > 3:Polar....

Btw, it's all in the documentation (commands.html)

Yeah Deep, thanks.

I have a new question now, is there any way I can extend r1-r6 to 37?

37? What do you mean?

If you mean r7, nope, there's a max of 6 args. When would you use 7?

You can always pass more args as variables, though.