String Model

Autodesk documentation sampled here supports a semantic view of strings, but not a full implementation-level storage model.

Accordingly, this specification treats a string as:

• an ordered sequence of characters,
• addressable by string-processing functions,
• readable and writable through string and text-I/O facilities,
• subject to version-dependent character encoding behavior.

This specification does not currently claim a vendor-documented internal representation such as:

• byte vector,
• UTF-16 code-unit vector,
• Unicode scalar-value vector,
• implementation-specific opaque text object.

At the current evidence level, only the observable behavior is normative.