search

redj / ecere-sdk

Ecere SDK (eC Language, Ecere IDE, Cross platform GUI, graphics, and more) — http://ec-lang.org —
http://ecere.org
Other
4 stars 1 forks source link

Railroad diagrams for ec grammar #4

Open mingodad opened 3 years ago

mingodad commented 3 years ago

I've did a dirty conversion of the ec grammar to be able to generate a railroad diagram for it with https://www.bottlecaps.de/rr/ui see attached the resulting ebnf and the generated navigable xhtml. grammar-rr.zip

mingodad commented 3 years ago

It doesn't compile on OSX "High Sierra" (probably with previous and subsequent ones). What's the latest development branch ? Is it possible to have the source of doc/tao.pdf to update it ?

Cheers !

jerstlouis commented 3 years ago

@mingodad See also the railroad diagrams that we have at http://ec-lang.org/grammar/ as well as the grammar cheat sheet at http://ec-lang.org/eC-grammar.txt

The latest official development branch is dev. The bleeding-edge / branch subject to be renamed or dissappear / commits subject to be amended & re-shuffled often branch is currently named cmssAndGLFixes. Both of these build successfully on Mac OS 10.13.6, which I understand to be "High Sierra". However you will need the dependencies set up properly. Note that running the Ecere GUI on OSX still requires XQuartz installed. See the Travis-CI build results here: https://travis-ci.org/github/ecere/ecere-sdk/jobs/757121754 Also see the Travis-CI configuration: https://github.com/ecere/ecere-sdk/blob/dev/.travis.yml Which seems to only need to install OpenSSL from brew. Although I assume the default Travis-CI also ensures a few things are set up, like the lastest XCode.

The Ecere Tao of Programming is currently a copyrighted work not under an open-source license. If you wish to submit corrections and/or suggestions for improvements, please e-mail them to me, and I will make sure to keep them for the next time I work on the book, but know that it might take me a while to get back to it.

Please also consider contributing to the API documentation (which does fall under the project open-source license), e.g. https://github.com/ecere/ecere-sdk/tree/dev/doc/ecere, which you can use the Documentor to update (after configuring the Documentation path to that writable /doc/ directory in your Git repository). Thank you!