Stavros Macrakis wrote:
> These look like important improvements. As a relative newcomer to the R
> community, I'm not sure I understand what the procedures are for such
> changes.
>
> In particular, does the fact that the changes were committed to R-devel mean
> that the changes have already been
Right, these warnings correctly go away with the changes currently in
r-devel.
As I said in my mail, I do want to port them to 2.9.1 and was waiting
for a little more testing.
(Also, I'm about to move back to the East Coast for the summer, and will
be out of touch for a few days next week. Se
These look like important improvements. As a relative newcomer to the R
community, I'm not sure I understand what the procedures are for such
changes.
In particular, does the fact that the changes were committed to R-devel mean
that the changes have already been reviewed and approved by R Core?
In released 2.9.0, we have been seeing warnings when installing sp, for
example:
Warning in .checkS3forClass(class...@classname, where, names(exts)) :
Some of the superclasses in the definition of class "SpatialPoints" have
apparent S3 methods.
DANGER: the new class will not inherit these meth
Changes were committed today to the r-devel version of R to make S4 and
S3 classes (and abnormal object types such as "environment") work
together more consistently.
Basically, S4 classes can now contain any S3 class or object type, and
should now inherit S3 methods for these. Also, the main
