> Can you explain this? The way I see this, the piece of code that does
> the actual aliasing is yours, and this piece of code is unaffected by
> aliasing alias_method or any other dirty trick, so a check in that
> piece of code should work perfectly for detecting if eval and consorts
> get aliased. Of course, this is a run time check and not a compile
> time check, but I think this is what Brent is proposing. Besides,
> there is no way you can check this at compile time because aliasing
> eval and consorts can be done in any single eval anywhere in the code.

What do you do about a method that was changed via eval that is already compiled and partially executed on your return call stack?

-John