>Entering destructed objects happens "all the time" when callbacks >to memberfunctions in already destructed objects are being called. >Normal Pike deals with this, and thus PIKEFUN's have to guard against >it too.
I really don't think this is particularly true considering that, at least as long as these callbacks are stored in an svalue, it is impossible to call a PIKEFUN in the destructed object as sval.u.object->prog will be NULL thanks to the object's destruction and it will thus be pretty impossible to look up and call the identifier in the program.
