From: R&S HUI
Sounds like you are using f. as a sort of subterfuge
to get around the lack of a more straightforward facility.
Maybe it is so, but this way is kind of blessed by the oop lab.
When you call the parent's method from within a child locale,
do you want the method to execute in the parent locale or the
child locale?
Actually, it is neither. Parent and child are "classes" and ther current
locale has to be "object". Unless, of course, we are trying to access
"static" property.
Or sometimes one and sometimes the other?
In oop it is pretty common practice when overriding method call parent's
method first (to do what parent usually does in this case) and then do your
child-specific part. (or, do child-specific part first, and then call
parent, depends). Now, this parent method may, in turn, rely on other
methods that may be overridden in a child, so just temporary removing child
class from copath may not be the answer.
Or perhaps executing it in the parent locale is an anathema.
Definitely. You do not want to execute (almost) anything in parent's or
child's locale, since it is a "class" and your modifiable data (aka
"proprties") is located in "object"
f. is not a complete answer, but it is better than nothing.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
