On Mon, Sep 5, 2016 at 11:38 AM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Mon, Sep 05, 2016 at 02:33:43AM +0200, Eliot Miranda wrote:
>> Hi Both,
>>
>>     the adoptInstance: code fails on V3 because of compact classes.  One cannot change a 1-word header instance if a compact class into a 1-word header of a non-compact class; there is no room in a 1-word header for the 32-bit non/compact class reference.
>>
>
> Hi Eliot,
>
> Right. You have documented this clearly in VMMaker. It is a reasonable and
> expected limitation.
>
>> David, fur give me for broaching what may be an emotionally painful topic.  I have no desire to cause you pain, but IMO this is important.
>>
>> We should /NOT/ hamstring code for either Spur or V3 with needless and expensive compatibility.  David, you're going to have to accept that the two will diverge.  Instead, try and think of a mechanism that supports tracking the differences instead of trying to keep the code bases the same. IMO effort put into keeping the two the same is effort wasted.
>
> My initial attempt to do this is http://www.squeaksource.com/TrunkUpdateStreamV3.
> For example, to see differences in the Collections package, use Monticello from
> trunk Squeak to look at differences in the Collections.V3 package in the
> TrunkUpdateStreamV3 repository. The other differences are in Compiler.V3,
> Kernel.V3, and System.V3 (along with the trivial difference in Files.V3 that
> was the subject of this thread).
>
> My question concerning the Files package arises directly from this. Aside
> from a single optimization in Files, all other significant differences
> have been contained within the Compiler, Collections, System, and Kernel
> packages.
>
>> Instead one could put effort into a Spur interpreter VM,
>
> I do not want to volunteer to start a new VM project until I finish the
> last one that I committed to do. I have said this before. And it's really
> just not someething that I can take on right now.

Dave, Just to clarify... If there happen to be a Context Interpreter
Spur VM, you would not be concerned about V3 compatibility?

cheers -ben