Thank you for the explanation; I saw that class definitions were
stored in package-level .__C__* and in a global cache
methods:::.classTable, but was not sure which was meant to be
definitive.
I'm hoping your bug fix will address identically named sealed classes
in different packages -- I hope to
Let's start from a simpler description, because the use of "sealed"
adds some confusion. Here's a basic version. I have two packages, P2
and P3, with different definitions of "myClass".
Classes with the same name on two packages are supposed to work, at
least for generating objects. There
I'd like to have two packages with S4 classes with the same name but
different implementation. To that end I create a package tmpA with
setClass("A",
representation=representation(
x="numeric"),
sealed=TRUE)
setClass("B",
representation=representation(
