Repository navigation
AlxLib 1.3.3
Patch release — the script engine's name lookup moves to the definition chain and gains the ^ activation anchor; link-load failures say why; and the shipped Linux bin/ is relocatable.
Name lookup follows the definition chain (1.3.3): a name resolves from the frame where its def was declared, not from the caller's stack, and every teardown path unwinds frames inner-to-outer. A chain may start with ^ / ^^, which moves the lookup to the enclosing callable's declaration frame (one level per ^). The four dot-path operations share one failure table, so a read, write, delete and call on the same shape report the same error, and a qualified call that misses now says where the name actually lives.
Link-load failures name the loader's reason: a failed link reports link error: <op> failed: <path>: <detail> on the on_csys channel and Cannot link: <path>: <detail> to the script — the platform loader's own text (dlerror() on Linux; the GetLastError() code plus its system message on Windows, with a short hint for a missing dependency, an architecture mismatch or a failed DllMain).
The shipped libraries carry $ORIGIN: every module DSO in the Linux package now resolves its siblings relative to itself (DT_RUNPATH is not transitive), so bin/ runs from any location; the example link modules link the engine and carry a relative runpath. doc/scpt/notice.md records the Linux and Windows deployment layouts — flat or shell + body, the /MD runtime, the dllexport entry points and the x64 contract.
The Lza GUI moves out: the example and its MSVC project leave this repository for the ALzapk repository.
Benchmark (2026-11-02): weighted GEOMEAN 206/311 (full-workload / pure-script weights), recorded in doc/scpt/bench.md.
No opcode or AST change: vtype is untouched, .axp products need no recompilation, and the SONAME stays .so.1.3.
Build packages — AlxLib-1.3.3-linux-x64-g80d2027-slim.tar.gz (+ .sha256): the public headers, the merged static library (lib/libalxlib.a, debug info stripped) and the notices; the shared libraries and per-module archives stay in the developer package and are not published. AlxLib-1.3.3-win-x64-g80d2027.zip (+ .sha256): the four DLLs, their import libraries, the headers and the docs, with AlxLib-1.3.3-win-x64-g80d2027.pdb.zip (+ .sha256) carrying the PDBs.