This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-17
Channels
- # bangalore-clj (1)
- # beginners (23)
- # boot (141)
- # cider (68)
- # cljs-dev (29)
- # cljsjs (1)
- # cljsrn (11)
- # clojure (150)
- # clojure-austin (3)
- # clojure-berlin (1)
- # clojure-france (2)
- # clojure-greece (13)
- # clojure-italy (5)
- # clojure-russia (49)
- # clojure-spec (15)
- # clojure-uk (45)
- # clojurescript (152)
- # code-art (1)
- # core-async (75)
- # cursive (12)
- # datascript (2)
- # datomic (90)
- # dirac (5)
- # emacs (10)
- # garden (1)
- # hoplon (52)
- # instaparse (4)
- # juxt (2)
- # lein-figwheel (2)
- # lumo (47)
- # mount (94)
- # off-topic (20)
- # om (21)
- # onyx (14)
- # parinfer (19)
- # pedestal (3)
- # protorepl (13)
- # re-frame (5)
- # reagent (20)
- # slack-help (10)
- # spacemacs (8)
- # specter (57)
- # unrepl (11)
- # untangled (3)
- # vim (1)
- # yada (1)
Thanks @aengelberg. I wonder if my <anything> was more complicated than that when I tried it. Hmm, there may be a useful project in "parsing" instaparse code into regex suitable for grabbing parsable chunks. I'm pretty sure instaparse is generating regex on the backend; but the capture-groups would need some editing.
that is not correct, instaparse parses context free langauges, which regexes cannot do
@hiredman I think I see what you mean. The problems I've been solving are probably simple enough that regex could define the same patterns. I suppose, getting into some real recursive stuff, it'd be less easy to go from instaparse-code to regex that says "grab a block of text that looks like this".