Pep and Nom

known bugs in the ℙ𝕖𝕡 ℕ𝕠𝕞 system

A document listing the bugs that I know about in the PEP / NOM system. This will include bugs in the pep interpreter and also translation scripts.

♛

you have to have a parse> label in a script, which seems silly but maybe not a bug.
For historical reasons the pep interpreter tool (which is written the c language uses 'byte' characters. So basically input-streams or files may not work probably with nom scripts when they are interpreted with
```
 pep -f script.pss input.txt
```
when I wrote “#* disable:” in a nom script the interpreter thought that disable was a command even though it is in a multiline comment.
The 'D' abbreviation for replace does not work because 'D' is not a valid command letter in bumble.sf.net/books/pars/compile.pss . Compile.pss probably should be rewritten with a new grammar.
classes like [.-] parse as ranges (i.e [a-z] ) not as lists