why is in TRSE : XOR , NOT

[funkheld]

hello good day.

why is in trse NOT , XOR ??

AND is & , Or is in the trse.

thanks
greeting.

[funkheld]

nobody knows how it works with the trse ????
why is in trse NOT , XOR ??


Thank you.
greeting

[Mike]

why is in trse NOT , XOR ?? [...] AND is & , Or is in the trse. [...] nobody knows how it works with the trse ????

Several possible answers:

1. Us Denial fellows quite likely were celebrating Xmas, hence the (relative) silence over the last three days,
2. Number of TRSE users is still small to those who prefer to program the VIC-20 on itself or use more established cross-developing setups (DASM, cc65, ca65, ACME, etc.) and don't feel the need to change to TRSE. Or, for that matter, would go and install TRSE just to understand what your problem is.
3. As I already wrote in another thread: the maintainers/developers of TRSE are unlikely to stumble across your question here in Denial. Asking in the relevant FB group or on github is much more likely to get their view upon design decisions.

But anyhow ...

why is in trse NOT , XOR ??

... from what I've gathered, AND and OR are also present. Together with NOT, these three operators are most probably intended for use in Boolean expressions, within IF conditions. "|" (bitwise or) and "&" (bitwise and) are there for working with 8-bit values, XOR is the corresponding exclusive-or operator (don't know about "^" as I thought it ought to be in the other thread). You'll have to check for yourself, whether NOT doubles as bitwise NOT operand, or "!" is used instead.

[funkheld]

hello, thanks for the held.

how is that written in asm please : NOT , XOR ??

then I tinker it with asm

greeting.

[AndyH]

Hi, and Merry Christmas. (I've been mostly away for a few days).

You can do this, check out the ASM produced, it just does EOR:

Code: Select all

	addbreakpoint();
	
	// XOR
	x := %11110000;
	y := %11001100;

	k := x xor y;
	
	// logical NOT
	k := x xor 255;

[funkheld]

hello thanks.

greeting.