[ddehilster]

Two fixes found while building the ICD-10 analyzers. Both used to fail silently.

Lazy *full.kbb keys from any pass

A *full.kbb stays on disk and is searched one key at a time, but only the tokenizer and dictfindword() could reach that search. A later pass calling findconcept() on the file's top concept found only keys the tokenizer had happened to load. down() and next() listed only those keys, so a scan of ICD head words silently missed codes.

• findconcept() / getconcept(): on a miss under a lazy file's top concept, they search that file and load the key with its whole block. Misses are remembered per file. Keys with a space, which SaveKB writes quoted ("heart attack":), are found too.
• down(): the first call loads the whole file, so every key is listed once and keys already loaded aren't built twice. findconcept() by position does the same.
• Tokenizer and dictfindword(): they now search a *full.kbb only if its top concept is dictionary or it has a same-stem .dict twin, so en-full.kbb with en-full.dict works as before. A domain KB such as an ICD index is no longer searched for every token and spelling candidate; that search took a spell pass from 0.1 s to 12 s. Its keys are also no longer registered as dictionary words.
  • Change for analyzer authors: dictfindword() no longer finds keys in domain files such as en-synonyms-full.kbb. Use findconcept() on the file's top concept instead.

"path" << x writes to an absolute path

The output operator put every file name under the input's _log folder, so G("$apppath") + "/out.txt" became <_log>/C:/.../out.txt. The open failed, nothing checked it, and every write was dropped with no message.

• An absolute path (starting with /, \ or a drive letter) is now used as given, as openfile() already does. A relative name still goes in _log.
• A file that can't be opened is reported once, in err.log and on stderr.
• The path was also formatted into a fixed 512-byte buffer with no bound; it is now a std::string.

Tests

• New fixtures kbb-lazy-lookup (nine checks) and output-path, run by one new step on Linux, Windows and macOS. On 4.3.15, kbb-lazy-lookup fails at its first check and stops at the kilo lookup.
• With the shipped en-full.kbb, en-full.dict and en-synonyms-full.kbb, the dicttokz parse tree of 15 copies of doj.txt is byte-identical to 4.3.15's.
• All local Windows fixture steps pass, except the compiled-analyzer step, which needs CI's packaged libraries. The parse-en-us tree is unchanged.

🤖 Generated with Claude Code