Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderA good question for any "macro" systems like this is something like the following: 1. Suppose you've written a function 'foo' in your language that does something useful (e.g.: partitions a sequence, validates a map, or pretty much anything really). 2. Some time later you want to write a macro 'bar'. 3. Can you use function 'foo' when writing 'bar'? If the answer to 3 is "no" then you don't really have Lisp-like macros. This is what makes Lisp macros…
> Why? Because a language without macros is a tool: You write applications with it. A language with macros is building material: You shape it and grow it into your application. Very nice! If only this could work with C++.
That's me! I was really naive about parsing back then and the "parser" is really not stellar.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 304
- Total comments
- 96
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2014-04-22 | Lisp macros for CFirst breakout · Best thread | eudox | 116 | 72 |
| 2016-03-17 | Cmacro | seansh | 8 | 0 |
| 2017-04-19 | Lisp macros for C | wooby | 113 | 14 |
| 2022-07-28 | Cmacro: Lisp Macros for CLatest 20+ point return | thesephist | 67 | 10 |