Thanks for the clarification Frederick. So if I am not wrong top level
class is nothing but in the Object level space, isn’t it?
Also your lack of response for my other question “how does these effect
the Dependencies mechanism?”, I am assuming it shouldn’t be a problem.
As we are asking ruby to look for the top level class, it is the same as
asking Filter.find() as in the case we would generally do when there is
no conflicting class is my situation.
And finally I am assuming from the your example (with my additional
Filter (same as self::Filter)
get_filter -> returns outer class Filter
get_my_filter -> returns Foo::Filter
get_outer_filter -> returns outer class Filter
so self::Filter depends in the context of self. Any corrections are
Frederick C. wrote:
On Jun 2, 3:36ï¿½am, Saty N. email@example.com wrote:
Thanks Ar Chon for the prompt response. But that runs me to another
How is Filter.find() different from ::Filter.find()?
::Filter makes ruby look from the top of the name space, so if you
then the :: means you get the top level Filter class rather than