Pep & Nom

Now I've heard there was a secret chord That David played, and it pleased the Lord But you don't really care for music, do you? Leonard Cohen

nom example scripts

/doc/doc.dir.index.html contains a list of scripts and documents in this folder.

Documentation for the NOM language and PEP virtual machine is in the /doc/ folder.

The scripts which begin with ro. are solutions (or attempted solutions) to problems on the www.rosettacode.org site. For example the script ro.balanced.brackets.pss solves the balanced_brackets problem .

examples can be run with the interpreter by typing


  pep -f eg/script.pss <inputfile>
  # or
  pep -f eg/script.pss -i <inputtext>

translate a nom script into go, compile and run


   pep -f tr/translate.go.pss eg/script.pss > script.go
   go build script.go
   echo "<input>" | ./script

Also the script /eg/nom.to.pss will translate a script with a simple prompt.

translate a script to 'rust' with nom.to.pss and compile (with rustc)

 pep -f nom.to.pss -i 'translate script.pss to rust'

Some scripts also have self-translation (for example /eg/json.check.pss and /eg/maths.tolatex.pss and /eg/text.tohtml.pss)

/eg/xml.parse.pss is an XML parser and error checker
/eg/nom.reference.syntax.pss is a syntax checker for the NOM language which provides precise error messages.
/eg/json.check.pss checks the syntax of a JSON text data file.
/eg/text.tohtml.pss transforms a “plain-text” (minimal mark-up) document into html
/eg/sed.tojava.pss transpiles a gnu SED script into the JAVA language (branch syntax with 't' etc is not supported because java has not [goto] statement )
/eg/maths.parse.pss parses and error checks arithmetic infix expressions.
/eg/maths.tolatex.pss transforms arithmetic, symbolic and logical expressions into printable L^AT_EX formulas.
/eg/exp.tolisp.pss transforms an arithmetic infix expression into LISP This is a simpler and older version of the 2 scripts above
/eg/toybnf.pss translates simple BNF type grammar rules into NOM scripts. This is the basis for a bnf style parsing and compiling language
/eg/natural.language.pss implements a limited natural language (English) parser. I plan to expand this with a better 'phrase grammar'
/eg/tocfoot.tohtml.pss demonstrates creating a table of contents and a footer (for footnotes) and using markers in the source document to place the table of contents and footers (this uses [toc] and [foot] as markers.

.noself. in the filenames means that there is no self-translation or self-help or self-testing in the script.
The scripts are often named for the format or language that they translate to such as text.tohtml.pss or nom.tolatex.pss
example scripts which begin with 'chat' provide a way (a sort of chatbot) to interact with another nom script or possibly a set of nom scripts. For example /eg/chat.timeline.pss should provide a chatbot which manages interactions with /eg/timeline.tohtml.pss as well as support functions related to this script, such as uploading or downloading data, editing and so forth.

faq formatting to html or pdf.
dictionary or glossary formatting: A script to format a plain-test dictionary into html and L^AT_EX using a standard dictionary format.
a drawing/animation language: or invent a new drawing/animation/gaming language (getting ambitious which has a slightly more sensible syntax than that of the “logo” language. I started this in /eg/drawlang.pss which transpiles to python, but I haven't continued.
an app-super-language which generated code for dart/flutter.