On 30 Jan 2004 at 14:05, John Chambers wrote:
> It was never the intention that validity checking happen automatically
> on _every_ assignment of an object from the class--since those
> assignments take place frequently during evaluation of functions, the
> overhead would be unacceptable. And as
It was never the intention that validity checking happen automatically
on _every_ assignment of an object from the class--since those
assignments take place frequently during evaluation of functions, the
overhead would be unacceptable. And as Robert points out, one needs to
postpone validity c
On 29 Jan 2004 at 20:04, Robert Gentleman wrote:
> There are some efficiency issues that prevent constant checking (at
> least at the present time). There are also some other issues that
> need to be adequately addressed too. For example, suppose I had an
> object with two slots
>a - a
On Thu, Jan 29, 2004 at 09:30:19PM +0100, Torsten Steuernagel wrote:
> I'm using R 1.8.1 (Win32, Linux) and have some difficulties using
> validation functions for S4 classes. The problem is if I specify a
> validation function with setValidity("myclass", validate.myclass) object
> validation is
I'm using R 1.8.1 (Win32, Linux) and have some difficulties using
validation functions for S4 classes. The problem is if I specify a
validation function with setValidity("myclass", validate.myclass) object
validation is only performed when I create an instance using
new("myclass"), or when I ex
