Initial Basis (tracking issue)

[ethanpailes]

All of the named unicode charicter classes should be bound to variables in an initial basis, and common expressions should be given sensible names. For example:

`[0-9]` => digit_ascii
`[0-9]+` => number_ascii
`\b\w+\b` => word

The definitions of this initial basis should be displayed prominently in the documentation (It may be worth writing a little script to gen both the docs and the code just to make sure that they never fall out of sync.). Once function support lands, we should add common functions like sep(e, e) -> e, term(e, e) -> e, comma_sep(e), semi_term(e), and so on. Until the infastructure is in place for that, new ideas for the initial basis should be added to this issue as a comment.

[tekknolagi]

Might be worth taking a look at the basis of Menhir

[ethanpailes]

That's a good idea. Glancing at this, I don't see much in the way of the sort of initial basis that I'm talking about. Do you know of a better place to look?

[tekknolagi]

Menhir manual. It's a PDF

On Thu, May 3, 2018, 22:53 ethanpailes notifications@github.com wrote:

That's a good idea. Glancing at this https://realworldocaml.org/v1/en/html/parsing-with-ocamllex-and-menhir.html, I don't see much in the way of the sort of initial basis that I'm talking about. Do you know of a better place to look?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ethanpailes/remake/issues/3#issuecomment-386494230, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYfDwRaAWhjepbrbvfNXjjO0yX4iZb8ks5tu8KegaJpZM4Tx0A9 .

[ethanpailes]

link for future reference.