These name are standardized and will not changed in the further, if the bounds is smaller (e.g. not including NUL terminator) there is a compiler error.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
May be sensible to share the C0 strings between SetRepresentations and ControlCharacterString and extract these to another module. Either in PositionCache as that is where SpecialRepresentations currently lives or into a new Representations module.
To me, adding bounds makes the code more fragile and difficult to modify.
These name are standardized and will not changed in the further, if the bounds is smaller (e.g. not including NUL terminator) there is a compiler error.
May be sensible to share the C0 strings between
SetRepresentationsandControlCharacterStringand extract these to another module. Either inPositionCacheas that is whereSpecialRepresentationscurrently lives or into a newRepresentationsmodule.Something like the attached patch.
Adding
SetDefaultRepresentations()looks good to me.Moved default representation code into
SpecialRepresentationsclass with [7cf62b].Related
Commit: [7cf62b]
The original feature won't be included.