Carl Mäsak

[Branch](https://github.com/masak/007/tree/ff-macro).

> The reason they're perfect is that they are actually operators with internal state. If we implement this right, the operator state should be per sub *clone*. This won't happen...

> I'm not clever enough today to nail down how this ought to work. But it needs to be something that re-enters the scope with the `active` variable whenever the...

> Leaving all concerns about un-hygiene aside for the moment And for when we feel up to solving the concerns about un-hygiene satisfactorily, there's a well-tested solution out there: EcmaScript...

Just slapped a "currently-blocked" label on this issue. It's one of our most desirable issues to have in place (since it's at the top of the #194 list) and yet...

I was toying around with having a class-based API for stateful macros. The `infix:` macro would come out something like this: return class { property lhs; property rhs; private property...

triumphant progress report: I have macro infix: working in the `ff-macro` branch need to do some (hopefully simple) cleaning-up, and then I can merge it to master this has been...

I'll have to take my November me's word for it that the `ff-branch` used to work... it doesn't now. $ bin/007 examples/ff.007 Variable 'v' is not declared [...] I haven't...

> I'm not clever enough today to nail down how this ought to work. But today, I am! 😄 The solution has been staring me in the face. I'm busy,...

Just dropping in here to point out a connection — previously not pointed out, I believe — between the statefulness of the `ff` family of macros, and the statefulness of...