From: Robert Feldt <feldt@...>
Date: 2002-02-19T17:59:37+09:00
Subject: Re: alias danger

On Mon, 18 Feb 2002, Yukihiro Matsumoto wrote:

> Hi,
> 
> In message "Re: alias danger"
>     on 02/02/18, Dave Thomas <Dave@PragmaticProgrammer.com> writes:
> 
> |> But now I remember why that makes me itch. It's tempting to think of
> |> this alias-and-redefine as an operation that is insulated from the
> |> rest of the world, but the binding effect of alias is, of course,
> |> not local.  Unless you choose a very obscure name for you alias, you
> |> run the risk of a stack overflow:
> |
> |That's always been an issue which has worried me.
> 
> Me too.  I'm thinking of a solution kinda similar to CLOS's before,
> after, around method combination, or in another words, defadvice in
> emacs lisp.  It will obsolete alias and undef, but will not appear in
> the near future.
> 
It would be awesome if Ruby got this. Really, really useful. Are you
thinking Rite/Ruby2.0 or even further into the future?

/Robert