bill lam wrote: > codestroy_pshape_ f. '' > is detrimental. If any instance calls "destroy", it will erase > locale 'pshape' itself, not the locale of the object. Any further > reference to pshape will cause syntax error because the locale > no longer exists. > > Of course, the above errors will not occur if script is not locked.
You are correct: in locked code, f. needs to happen before the code is locked. I can't think of any way around that issue. > IMO COCLASSPATH is the correct way to implement class inheritance > because it keeps the static parent-child relationship. coninsert/ > copath is a dynamic attribute that is not related to inheritance. > For example, it is possible at any time, add or delete another class > in copath, on the other hand class inheritance is a static relationship. > As COCLASSPATH is already hidden from user, I can not see any material > need to decommit it. I don't understand what you've written here. Can you rephrase what you've said from my point of view? Here's how I see things: (1) COCLASSPATH is not hidden from the user. (2) COCLASSPATH can be manipulated dynamically just as easily as copath (3) if it's understood that the copath of the class is what the object will inherit, then the progammer should not manipulate that copath in irrelevant ways. Thanks, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
