#17 Bad method names in "Class" class

Features
closed-accepted
Annoyances (7)
6
2004-11-18
2004-11-12
Francesco Garosi
No

There are two functions in Class that have deceiving
names, due to a misinterpretation of the underlying low-
level functions. Namely the interface functions are:

SubclassMessageHandlerList()
PrintSubclassMessageHandlers()

which actually do not operate on subclass message
handlers, but on the message handlers of the class they
are attached to including the ones that the class
inherited. The documentation also reports the wrong
behaviour.

These functions should be renamed respectively to:

AllMessageHandlerList()
PrintAllMessageHandlers()

in order to show that they operate on all message
handlers and not only on the ones that are defined for
the examined class. The documentation should be
updated accordingly.

Discussion

  • Logged In: YES
    user_id=328337

    The fixes for this bug or request have been accepted and
    committed to current CVS tree: next release will include these
    fixes, possibly among other enhancements.

     
    • status: open --> closed-accepted