Seth Falcon wrote:
John Chambers [EMAIL PROTECTED] writes:
As I mentioned, this relates to writing methods for initialize().
Imagine someone else extends the class Ab, for which you wrote a
method. If they add slots to their class and you do not pass down ...
to callNextMethod(), then
Herve Pages wrote:
More generally I don't see what's wrong with not passing
to callNextMethod all the arguments coming from the call
to new:
setClass(A, representation(toto=integer))
setMethod(initialize, A, function(.Object, toto0) [EMAIL PROTECTED]
- as.integer(toto0);
John Chambers [EMAIL PROTECTED] writes:
As I mentioned, this relates to writing methods for initialize().
Imagine someone else extends the class Ab, for which you wrote a
method. If they add slots to their class and you do not pass down ...
to callNextMethod(), then you have blocked users
A problem with callNextMethod, which is caching an inherited method as
if it was not inherited, causing confusion on the next search. Should
be fairly easy to fix, but may be a while before I get time to do so.
By the way, I hope your simplified example does not reflect what happens
in the
Hi John,
John Chambers wrote:
A problem with callNextMethod, which is caching an inherited method as
if it was not inherited, causing confusion on the next search. Should
be fairly easy to fix, but may be a while before I get time to do so.
By the way, I hope your simplified example does
Hi again,
Here is a very simplified version of a class hierarchy
defined in the Biobase package (Bioconductor). I post
here because this seems to be an S4 related problem:
setClass(A, representation(name=character))
setMethod(initialize, A, function(.Object) [EMAIL PROTECTED] - I'm
