[bug #41111] C++ destructors not called correctly in finalize breaking objc_setAssociatedObject

[Richard Frith-Macdonald]

Follow-up Comment #1, bug #41111 (project gnustep):

I'm confused.
As far as I can see the two code snippets should have identical effects.
Both step up the class hierarchy, and both call each destructor implementation
found.
The only difference seems to be that one stops traversing the hierarchy after
the last destructor is called, and the other continues traversing the
hierarchy up to the root class.
However, the destructorClass variable is not used … after this, so whether
its the first superclass without a destructor or the root class doesn't
matter.

Unless … perhaps this is illustrating some bug in class_respondsToSelector()
?
Are you saying that this is returning NO for some cases when it should return
YES?
My understanding is that this function should return YES if instances of a
class respond to a selector (ie if the method is implemented by the class or
by any of its superclasses).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41111>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/