RE: [SERVER] chparent()

• Date: Thu, 21 Mar 1996 12:43:38 PST
• From:
  "Seth I. Rich" <sir@po.cwru.edu>
• Content-Type: text/plain; charset="us-ascii"

>> I know that it is so with create(), but when a chparent() is done,
>> does the :initialize() verb on the changed object get called?
>> If not, why?  And, if there is no reason why this would be a
>> bad thing, I'd like to add it to the wish-list for future servers...

>I did once have a proposal (see 9/92) about the Right Thing to do with
>:initialize/:recycle.
>Summary:  Life gets easier if you view create()/recycle()/chparent() as
>a sequences of atomic
>   specialize() -- chparent to sibling, call :initialize
>   generalize() -- call :finalize, chparent to grandparent
>operations, accepting the possibility of create(), recycle(), or
>chparent() bombing out in the middle if some :initialize/:finalize
>raises an exception.  This may even be more palatable now that one can
>finally do exception handling.  

I hacked this together on OpalMOO once.  It confused enough people that
I turned it off and we went back to (mostly) vanilla chparent().  If
anyone's interested in the code (which worked when tested, but no promises),
I can make it available.

I very much like the idea of stepwise chparent()ing.

Seth / Blackbriar
----------------------------------------------------------------------
Seth I. Rich - sir@po.cwru.edu
                                 There is nothing more precious than
Rabbits on walls, no problem.    a tear of true repentance.

• Prev: RE: [SERVER] chparent()
• Next: [SERVER] huh stack in tracebacks
• Index: MOO-cows
• Thread: MOO-cows