You may also be able to write an instaparse grammar for EBNF (a
grammar of grammars)—Loner contains a parser-combinator-style EBNF
parser, so it's certainly do-able.
Then you could use that parser to parse your grammar—presumably the
parsers yield trees on input-strings.
D. Ben Knoble
On Sun
I should clarify: it parses a variant of EBNF. The specific syntax is
explained at https://benknoble.github.io/loner/
and https://benknoble.github.io/loner/demo.html#syntax
On Saturday, July 17, 2021 at 8:50:48 PM UTC-4 D. Ben Knoble wrote:
> I haven't touched Clojure in a year or two, and
I haven't touched Clojure in a year or two, and I'm not familiar with
instaparse.
I can say, from a terminology stand-point, that a grammar (such as one in
EBNF) can produce a parser, which then produces parse-trees of input
strings. So, perhaps you mean that you want parse-trees of strings in
Thanks, super helpful. I'll follow-up if I have any questions.
D. Ben Knoble
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderate
I've started seeing a lot of messages like this, I think after I updated
clojure, but I can't find any documentation or points in the changelog
about the change, why I'm getting this message, or what the correct fix is.
I know it provides a change I can make, but is it the right one?
Some
