Re: Crazy macro

This may be The Real Problem. A more functional attitude would clean up
your code nicely, making all this unnecessary.

I have a very functional attitude, as far as I know. I think the
issues are orthogonal. When I used the word "state" I didn't mean it
in the way you think (but I can't really think of a better term).
Suppose you are computing N intermediate values on the way to a final
result. You need to store them in local variables, but that doesn't
mean you need assignment statements. If you insert a subroutine just
to break up the flow, you're going to have to write something like

(multiple-value-let (v1 ... vN)
(sub v1 ... vN)
... resume ...)

or perhaps

(multiple-value-call #'sub2 (sub1 v1 .... vN))

This is all perfectly functional, and perfectly hideous.

-- Drew

.