Implementation Guidance

clautolisp should model strings as abstract text objects with versioned observable behavior, not by prematurely committing the specification to a specific Common Lisp string implementation detail.

The implementation should provide at least:

• a legacy compatibility mode for pre-Unicode behavior,
• a Unicode-aware mode corresponding to modern Autodesk behavior,
• explicit control through dialect/environment/profile configuration,
• compatibility tests for character-code, indexing, file I/O, and search functions.

This is especially important because Common Lisp string behavior is implementation-dependent enough that naive reuse could leak incorrect semantics into AutoLISP compatibility.