Skip to content

Help: -DICTSOURCE (4.2.33) #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ddehilster merged 1 commit into from
Oct 15, 2026
Merged

Help: -DICTSOURCE (4.2.33) #244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions Help/markdown/VisualText_Basics/About_the_analyzer_sequence.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,19 @@ Splitting is done first, then joining, then phrases. A token made by **split** o

**join**, **split** and **_name** lines are **NEW 4.2.30**.

**Finding the entry behind a node.** Run the engine with **-DICTSOURCE** and every node built from a **.dict** entry gets two more attributes: **dictfile**, the file's name, and **dictline**, the entry's line. A token made by **join** or **split** gets the line of that entry, unless the word it spells has its own entry. A word on several lines keeps the first. Entries in a lazily loaded **\*full.dict** have no line number, so they get only **dictfile**. The attributes are ordinary ones (`pnvar(n, "dictline")`), and a KB saved during such a run keeps them. Without the switch nothing is recorded, so normal runs pay nothing for it.

```
nlp -ANA myanalyzer -WORK C:\nlp-engine -DICTSOURCE input.txt
```

```
_bridge [19,25,...,node, ("type" "location") ("kind" "raised") ("dictfile" "words.dict") ("dictline" 14)]
viaduct [19,25,...,alpha, ("kind" "raised") ("dictfile" "words.dict") ("dictline" 14)]
```

**-DICTSOURCE** is **NEW 4.2.33**.

## Comments in analyzer.seq

A **#** starts a comment that runs to the end of the line, and each pass line normally carries one. C-style block comments, **/\* ... \*/**, are also allowed and may span several lines:
Expand Down
Loading