@neauoire could you help me understand the convention here? why 8// and 8** instead of 8/ and 8* ?

· · Web · 1 · 0 · 0

@aw so i think @neauoire has pretty much moved away from macros at this point, not sure there's an "active" convention here.

but i think the intent was to convey that the operators worked on two bytes (16-bit values). so 8* would be the 8-bit version and 8** would be the 16-bit version.

(i never used this myself.)

@d6 @aw yeah, this was only useful to help me remember that #30 SFT was equal to #08 MUL, and so on. Nowadays, I know them by heart, and uxnlin warns me if I use mul where a sft could be used.

@neauoire @d6 @aw I've recently removed all the macros which were just symbols (like "++" for "ADD2") when some of these symbols were used for extra runes.

I stopped short of removing these "8//" macros because I thought they might be more easily understood than "#03 SFT2", but maybe the latter is the clearest after all?

@alderwick @neauoire @d6 Interesting! I am playing around with a forth that targets uxn and wondering what conventions to bring over. thanks!

@aw @alderwick @d6 I wouldn't carry these over, but you might want to consider using bit shifting for mul/div, just as an exercise to understand how numbers map to binary data :uxn:

@neauoire @aw @d6 Thanks for the feedback! I'll remove them from the repo 😊

Sign in to participate in the conversation

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.