Dan Sugalski wrote:
> But, if we toss refcounts, and split GC cleanup and
> end of scope actions anyway, we need to have a mechanism to hoist things
> out of the current scope.

Why say hoist when we can say return? I can think of several ways of
returning values that don't require the caller to allocate a binding for
the return value. Variants of the existing perl 5 stack push would work
fine. We could also use a special "register" variable that return values
are shoved into.

None of these require the hackery of Tcl's upvar.

Shouldn't we adopt a policy of never adding stuff to Perl 6 the language
just because it'd be easy with a particular release of perl 6 the software?

- Ken

Reply via email to