[Vm-dev] [squeak-dev] Error in ImageSegment primitive?

[Max Leske]

> On 10 May 2017, at 01:14, vm-dev-request at lists.squeakfoundation.org wrote:
> 
> NativeImageSegment sounds good.

+1

> 
> (I had renamed "my" class to OldImageSegment but ran into issues with old
> code breaking. Better to start clean)
> 
> - Bert -
> 
> On Tue 9. May 2017 at 23:05, Eliot Miranda <eliot.miranda at gmail.com <mailto:eliot.miranda at gmail.com>> wrote:
> 
>> 
>> Hi Max, Bert,
>> 
>>    to integrate the below with Bert's rewriting of the importer, I'm
>> thinking of renaming ImageSegment to NativeImageSegment.  Hopefully we can
>> get the native and the all-in-Smalltalk code to coexist.  Is
>> NativeImageSegment a good name?  Do you prefer e.g. VMImageSegment?
>> SpurImageSegment?
>> 
>> And we still have to handle fixing up of loaded objects.  The load
>> primitive answers the array of roots.  We'd actually like an array of all
>> loaded objects.  Maybe I should add a variant of the load primitive that
>> does this.  Are you, Max, up to rewriting the post-load object mixup to
>> avoid nextObject?

Yes, I can do that. I'll probably need some help but I think I can handle it.

Max

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20170510/d17d3ae2/attachment.html>