identifying new not inherited methods

[malkarouri at gmail.com]

George Sakkis wrote:
[...]
> You're looking at it backwards; there's no particular reason this
> should be a method of class A since it can be used for any arbitrary
> object with no extra overhead. Now, if you intend to use it only for
> instances of A and its subclasses, the only difference would be
> syntactic; if you prefer x.list_cmds() from list_cmds(x), go with the
> method.

You are right of course. Let's say it's just bad company; the group I
am working with are mainly Java developers.

k