[Nitro] advice.rb

Trans transfire at gmail.com
Wed Sep 5 15:00:05 EDT 2007

On Sep 5, 11:28 am, Trans <transf... at gmail.com> wrote:
> On Sep 5, 11:20 am, Trans <transf... at gmail.com> wrote:
> > Considering the alternatives (Proc.bind or myriads of method
> > definitions), it may be best to accept this limitation for the time
> > being. If one has to access an instance var in an advice block then
> > one can always make an accessor to it, which, of course, works fine.
> No... I'm actually wrong about that. This has to be fixed b/c not even
> instance methods are accessible. Damn it. Alright, well, I'll just
> have to define methods.

See the crazy methods ;)

["inspect", "out", "clone", "x:before-605787008", "method",
"public_methods", "instance_variable_defined?", "equal?", "freeze",
"methods", "respond_to?", "method!", "x:after-605787178", "dup",
"instance_variables", "x", "__id__", "eql?", "object_id",
"to_yaml_style", "x:before-605774938", "id", "singleton_methods",
"send", "taint", "x:around-605787338", "frozen?",
"instance_variable_get", "__send__", "instance_of?", "to_a",
"to_yaml_properties", "type", "x:after-605783528", "to_yaml",
"protected_methods", "instance_eval", "==", "display", "x_origin",
"===", "instance_variable_set", "kind_of?", "extend", "to_s",
"taguri", "out_origin", "hash", "class", "tainted?", "=~",
"private_methods", "taguri=", "nil?", "untaint", "is_a?"]

Okay, well it works good. A little faster too, despite the crufty
methods. Only one question, is this the right execution order?

  ["BEFORE Y#x", "BEFORE X#x", "Y#x", "X#x", "AFTER Y#x", "AFTER X#x"]

or should it be:

  ["BEFORE Y#x", "BEFORE X#x", "Y#x", "X#x", "AFTER X#x", "AFTER Y#x"]


More information about the Nitro-general mailing list