TBtbatchelli·Jan 12, 2015
Not to be confused by Christopher Grand's clojure parser library:
https://github.com/cgrand/parsley
In Parsley: a simple language for extracting structured data from web pagescgrand
parsley
Clojure2012–2015
cgrand / parsley
parsley
a DSL for creating total and truly incremental parsers in Clojure
2Distinct people
2Mentions
0Explicit recommenders
203GitHub stars
What to know before exploring
What it is
a DSL for creating total and truly incremental parsers in Clojure
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year2 dated mentions
Observed mentions: 2012-04-14 20:21:22 UTC to 2015-01-12 01:32:32 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesHaving poked around with Jeremy's compiler (I forget if I've sent in patches or not), I'm curious about some of the technical details behind the project. I've thought about this topic for a while and this is a rather disorganized brain dump Feel free to respond to as much or as little as you like.
The main complaint I have with the current compiler is the inability to control output either via compile time macros or compiler hooks. I would like to map Coffeescript's class construct onto the class system of a variety of frameworks. I understand most of Jeremy's rationale but I still have to patch my install to change the superclass name in order to map coffeescript classes onto yui3 (same pattern, different superclass names) and I'd really like to see the class syntax map to Ember's classes.
Any particular reason for PEGs over Parser Combi
Read the rest
nators?
From reading, looks like you plan to skip the rewriter pass. I started a PEG parser implementation in the 0.3 timeframe but ran into problems with the `x = a: 1, b, c` -> `x = {a: 1, b:'b', c:'c'}` and similar ambiguities. Do you have a plan for handling this? Will you drop language features if you can't do them without rewriting?
What sort of compile time hooks are you planning? Just (C)AST->(J)AST passes?
In the time since I've messed with coffeescript internals, I've run across two potentially useful things that I haven't really investigated:
* http://www.mirah.org/wiki/Macros <- macros in a non-lisp langauge
* https://github.com/cgrand/parsley <- fully incremental parser generator
The latter is interesting because it'd potentially allow the actual compiler to be used as the starting point for language IDE support.
Good luck, I'll be following your progress with interest.