I don't think that this scenario can come up in any other case than an upgrade, but IF Rowan could detect that the superclass of a class is the latest version of the class, I could avoid what I imagine to be some nasty hijinks to force it to happen ...
Hit this during upgrade from 3.6.4 to 3.7.0 where there is a new version of GsFileIn and the Rowan subclass GsFileinPackager was not properly attached to the new version during a normal Rowan load ...
I don't think that this scenario can come up in any other case than an upgrade, but IF Rowan could detect that the superclass of a class is the latest version of the class, I could avoid what I imagine to be some nasty hijinks to force it to happen ...
Hit this during upgrade from 3.6.4 to 3.7.0 where there is a new version of GsFileIn and the Rowan subclass GsFileinPackager was not properly attached to the new version during a normal Rowan load ...