4 ms·
The fact that it's a single bit confuses me. If it was a full null byte (0x00) it would be easier to explain. C strings are null terminated, so you could assume
by doix 5y ago
The fact that it's a single bit confuses me. If it was a full null byte (0x00) it would be easier to explain. C strings are null terminated, so you could assume the editor stopped reading when it hit "the end of a string" but BASIC still executed it?
Or if it was some unreadable ASCII character, maybe it worked like an EOF in the editor? But the fact that he switched it from an F to an E gives me no clues. This stuff is unfortunately before my time, I'm sad I never got to play around with stuff like this in my youth.
- HotHotLava 5y agoThe byte apparently was not part of the file contents but part of a file header that was interpreted by the editor; probably encoding some kind of "file type" that was displayed differently when opened. However, technically, switching an 'E' for an 'F' is flipping *two* bits :/
- johnday 5y ago0xe to 0xf is a single bit flip.
- deleted 5y ago[deleted]
- Symbiote 5y agoSome older filesystems, like ADFS[1] which I'm familiar with, have a "type" attribute, along with the read/write/execute (etc.) bits, as part of the directory node [2]. On RISC OS, as that page says, a BASIC file has type FFB. I remember a plain text file had type FFF. [1] https://www.kernel.org/doc/html/latest/filesystems/adfs.html https://www.kernel.org/doc/html/latest/filesystems/adfs.html [2] https://docs.huihoo.com/doxygen/linux/kernel/3.7/adfs_8h_source.html https://docs.huihoo.com/doxygen/linux/kernel/3.7/adfs_8h_sou...