Thank you for making that. There are are articles that mention how we forgot the octal connection to the x86 isa. Your ascii art table is just a really clean way of visualizing it.
Interestingly, many old workstations that did 3d (primarily SGI), had what was called an overlay plane. This was essentially a separate frame buffer using indexed color into a palette. One of the colors would indicate transparency. The overlay was traditionally used for all UI or debug output on top of a 3d scene. For example, the Alias/Wavefront 3d modeler required this feature in order to run. It allowed the slower 3d hardware of that era to focus on a complex scene vs the scene AND the UI.
Strangely enough, I was researching a related topic a few days ago. I was wondering if disassemblers did the right thing with these opcodes. I was wondering in particular if they could reproduce the exact binary after disassembly.
It turns out that most assemblers do not have a specific way to make a distinction. The gnu assembler (gas) does have a ‘.s’ suffix for mnemonics to differentiate.
At a job I had, they gave people a book titled: Your Mac Is Not A Typewriter
One of the big things was the single space rule.
Interesting thing tho. Many years later I read on Steve Losh’s blog that he uses two spaces after every period. Why? So he can just do a simple search to move through sentences.
Hi msbarnett: sorry unrelated to this thread.
In an older thread you mention an acronym TFA. The thread was a discussion on sparse files and removing bytes from the front of a file.
What is TFA?