2006-01-05 23:59:02 UTC
I've been using Retroweaver 1.1 for several projects internally, and recently discovered Retroweaver-NG. I'm in the middle of transitioning projects over from Retroweaver 1.1 up to the Retroweaver-NG 1.2.2 release. Some of these projects interact with each other in such a way that binary compatibility is required between each other.
My question is, if I've weaved a project using Retroweaver 1.1, should I expect any difficulty when using the weaved classes against the 1.2.2 runtime library? From what I can tell, the only significant difference in the runtime libraries that might be relevant is the addition of final modifiers in class and method signatures.
If the runtime library is indeed compatible with Retroweaver 1.1 weaved classes, is this a deliberate design decision that can be relied on for future releases, or is it an accident of fate? For future migrations, it would be good to have a clear path to follow.
