Hi John,
John Chambers wrote:
> The "infelicity" arises because validObject() is not a generic function;
> validity "method" is a bit of a misnomer.
Indeed. And I guess referring to "method dispatch" like I did in my previous
email is not appropriate either.
So yes I learned that thinking of val
The "infelicity" arises because validObject() is not a generic function;
validity "method" is a bit of a misnomer. The functions are attached to
the class definition and validObject looks for them directly--in the
process it catches all methods from superclasses, but not from
superclasses of t
Hi,
When called with complete=TRUE, validObject() is supposed to work in a
recursive manner. But here is a situation where it doesn't seem to be
the case.
Let's define a class with a validity method:
setClass("PosInts", representation(ii="integer"))
setValidity("PosInts",
function(ob
