After over 15 years of vpa use I want to put a new mnemonic for bit set, bit clear, bit change, and for bit test.
The old ones are CPU32 legacy - with extended source/destination addressing capabilities. So they are (let's do just bit set): bset[.size] ,[source1], (or sort of). For example:
bset.l #0,(address) will read the longword (32 bits) at address, test its least significant bit (bit 0 here), set it to 1 and write back to address (or bset.l- if test is not wanted).
Now I want to add a mnemonic doing the same but in big endian form; meaning bit 0 will be the most significant bit at (address).
I did "bebset" (big endian bit set) after a few seconds of thought, I had to implement it digging in 15+ years old code, took me hours to recall things so naming was not high on my radar at the moment.
I am not sure I like it, please come up with suggestions. I spent may be 5 minutes thinking and thought of nothing better so I wrote this. I don't like "bebset" because it is somewhat lengthy, and it does not feel nice enough I suppose... Then making it too similar (say something like "bits") will be a source of errors, confusing the big for the little endian one etc. May be bbset? Can look like a keybounce error....
Thought I'd sleep over it (going to bed now) as I'll probably live with it for a while once I adopt it.
Dimiter
------------------------------------------------------ Dimiter Popoff, TGI
------------------------------------------------------