3 ms·
I don’t know. Can you tell me? ;)
by Robotbeat 6y ago
I don’t know. Can you tell me? ;)
- TeMPOraL 6y agoThe bits that aren't used don't correspond to printable characters :).
- tdeck 6y agoI assume the parent is referring to the various control characters like "START OF HEADING", "START OF TEXT", "RECORD SEPARATOR", etc... I haven't seen most of these used for their original control purpose but they date back a long way: https://ascii.cl/control-characters.htm https://ascii.cl/control-characters.htm
- hakfoo 6y agoI've seen them in some vendor-specific data formats in the financial space. They seem to be from an era when the formatting models were either fixed-width fields, or a serial set of variable width fields delineated by FIELD SEPERATOR, GROUP SEPERATOR, etc. What both models lacked was a good way to handle optional/sparse fields. If you have a data structure with 40 sub-fields, a JSON, XML or YAML notation can encode "Just subfield 26" pretty efficiently, but the FIELD SEPERATOR model usually involves having dozens of empty fields to space the one you want, and a lot of delicacy if the field layout changes.
- colejohnson66 6y agoThe “C0” block (U+0000 through U+001F) https://en.wikipedia.org/wiki/C0_and_C1_control_codes https://en.wikipedia.org/wiki/C0_and_C1_control_codes They’re almost never used in practice however.