Andreas Raab wrote:
b) Use your current build environment and #define VM_PROXY_MINOR to be the minimum version you can get away with (i.e., the minimum version the plugin compiles with).
Wow! Approach (b) did the trick! I only needed to increment by 1.
Sneaky but effective :-)
Not sneaky at all. The interface is designed in such a way that you can compile for older proxy versions if you'd like to.
Hmmm... I see what you're saying. But I only recompiled the VM, pretending that it has a minor-version of 6 when in fact it only includes the changes up to 5. That's surely sneaky, in general... though in this case I have the source code of the newest VM and of the plugin, and a quick look suggests no major code-breaking changes between 5 and 6.
And the test cases all run, so something must be happy.
Thanks again
Aran
Aran Lunzer wrote:
Not sneaky at all. The interface is designed in such a way that you can compile for older proxy versions if you'd like to.
Hmmm... I see what you're saying. But I only recompiled the VM, pretending that it has a minor-version of 6 when in fact it only includes the changes up to 5. That's surely sneaky, in general... though in this case I have the source code of the newest VM and of the plugin, and a quick look suggests no major code-breaking changes between 5 and 6.
Ouch. I meant recompiling the plugin with a lower proxy version, not the VM with a higher one. The way you're running now you'll crash if you ever run into a plugin which uses newer features.
Cheers, - Andreas
squeak-dev@lists.squeakfoundation.org