T
Trans
Well, silly me, I just realized what I suppose is THE issue with
capitalized methods serving as proxies for modules/classes.
To put it in context, I was working on Parametric mixins, such that
some #Includable() returns Includable after defining the parameters in
"self". It works great except...
The scope lookup of methods is not the same a constants.
That's kind of a shame, this is such a useful technique, in my
opinion. Now I would be just as happy to use Includable#[] instead,
but without a Binding.of_caller it is not possible.
So, assuming we are still ideologically opposed binding-of-caller what
do others think of the idea of capitalized methods having the same
scope lookup as constants?
T.
capitalized methods serving as proxies for modules/classes.
To put it in context, I was working on Parametric mixins, such that
some #Includable() returns Includable after defining the parameters in
"self". It works great except...
The scope lookup of methods is not the same a constants.
That's kind of a shame, this is such a useful technique, in my
opinion. Now I would be just as happy to use Includable#[] instead,
but without a Binding.of_caller it is not possible.
So, assuming we are still ideologically opposed binding-of-caller what
do others think of the idea of capitalized methods having the same
scope lookup as constants?
T.