Thanks Xavier. I realize implementation differs. Clearly I can't tap into
the underlying constant resolution with pure Ruby. But I expected that I
should be able to emulate it effectively with const_missing --I would think
it would possible to get essentially the same results.
The only difference I am sure about at this point, is that I haven't been
able to find a way to get `Module.nesting`, instead I had to resort to
Constant#name and splitting it up. Yet I thought this would give me a
superset of current functionality, not a subset. i.e.
class Foo
HERE = "here"
class Bar::Baz
HERE
end
end
Ruby's constant lookup would not find HERE, my code would.
Obviously, I am still missing something. And maybe you are right, that it
is not possible (which would be sad, imo). I just wish I knew what it was.
-- You received this message because you are subscribed to the Google Groups
ruby-talk-google group. To post to this group, send email to
[email protected]. To unsubscribe from this group, send email
to [email protected]. For more options, visit this
group at https://groups.google.com/d/forum/ruby-talk-google?hl=en
