Choosing and documenting some syntax for our initial -prebootstrap- scripting language
Remember that syntax is not important (but we need some which pleases to all of us; I hate the significant spaces of Python whose semantics is close to Scheme's), semantics is important. That scripting language will only be used in our GTK based IDE (to be written) handling the persistent store.
We could script RefPerSys in Guile, but I tend to believe that not using Guile but coding our own ad-hoc interpreter (semantically Guile or Lua like) is simpler. I could patch Guile for our usage (make it GTK friendly) but I am not entirely sure it is worth the effort. It could be tricky (and more than I thought initially).
If someone is interested in designing a simple syntax for a simple language inspired by Guile, Lua, or even simpler, I would be happy.
The thing is of course to specify that syntax in EBNF with more explanation in English -git commit
in some future section of refpersys-design.tex
- my guile-tutorial could be inspirational and of course you can reuse any part of it. Then git commit
a parser for that syntax. You could use flex + GNU bison or some other parser generator like lemon or something else (e.g. your own hand-written recursive descent parser coded in C).