This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-09
Channels
- # beginners (22)
- # boot (80)
- # cider (6)
- # cljs-dev (5)
- # clojure (190)
- # clojure-berlin (5)
- # clojure-dev (24)
- # clojure-italy (14)
- # clojure-russia (70)
- # clojure-spec (39)
- # clojure-uk (82)
- # clojurescript (121)
- # clojurewest (1)
- # core-logic (2)
- # cursive (25)
- # datascript (186)
- # datomic (33)
- # dirac (266)
- # emacs (9)
- # gsoc (4)
- # hoplon (37)
- # immutant (34)
- # instaparse (22)
- # jobs (4)
- # juxt (6)
- # lambdaisland (2)
- # leiningen (1)
- # liberator (1)
- # luminus (5)
- # lumo (28)
- # off-topic (9)
- # om (23)
- # onyx (26)
- # other-lisps (1)
- # parinfer (39)
- # pedestal (45)
- # proton (1)
- # protorepl (10)
- # re-frame (18)
- # reagent (4)
- # ring-swagger (8)
- # rum (4)
- # specter (13)
- # test-check (14)
- # testing (1)
- # unrepl (164)
- # untangled (10)
- # yada (14)
@bherrmann: in comparison, instaparse is slow and memory-inefficient, but far easier to use and accepts more types of grammars
I've never actually used ANTLR so I'm just guessing on both points
We have a large oracle grammar… in ANTLR and I’m curious about using instaparse instead
So it's already working in ANTLR?
Why would you want to switch?
(genuinely curious)
by when we make changes to the ANTLR grammar, it generates a java file which is too big to be compiled
so at the moment, we have to giggle the rules to keep the output small enough to be compiled.
well, it that old song of someone understanding how ANTLR v3 works and them leaving the company....
I’m working with a modified version of this http://www.antlr3.org/grammar/1209225566284/PLSQL3.g
I should really read this https://tomassetti.me/antlr-mega-tutorial/
The is_sql
thing actually looks like something unique to ANTLR (not standard BNF)
i.e. setting local variables