"David L. Nicol" wrote:
>
> POST{stuff} is a macro for
>
> push (my) @Deferred_stuff, sub {stuff}; # my on first use in a space
Since the reference implementation requires try, @Deferred_stuff is
actually try's argument list (a bunch of tagged catch and finally
blocks). The "my" is provided by
James Mastros wrote:
>
> You seem to like a /lot/ of context markers for
> line-of-flow-control. I think that's somwhat misguided.
I have not anywhere suggested that I'm against POST blocks; in fact
RFC 88 supports the similar "always" concept mentioned by RFC 119.
I'm just trying to figure out
On Mon, Feb 12, 2001 at 01:58:57PM -0700, Tony Olekshy wrote:
> - It does have in-flow presence, so it doesn't suffer from the
> problem that "always" has; POST is a statement, not a dangling
> clause. That fixes my main complaint with RFC 119. On the
> other hand, now there's noth
