Martin and Kevin,
Perhaps a variant of methods which more directly addresses the use-case
Kevin mentions might be in order?
I am happy to prepare a patch which implements a methodsForObj function
(name very much negotiable), or a third obj argument to methods which takes
the actual object and ans
I think this would be a good change. I think most users use the
'methods(class = <...>)' function to answer the question, "what
methods can I call on objects with these classes?", and in that
context I think it would be sensible for the function to accept more
than one class.
Kevin
On Wed, Oct 17
