Re: Status of Strongtalk C++ code: VM stability and progress on a graphical debugger

On Sun, May 18, 2008 at 7:16 PM, Shaping <[email protected]> wrote:

>
>
>  The other place it is
> > used is in the deserializer, which is pretty central to our take on
> > deployment.
>
> But we do need it for serializing instances and source code?


We use become: or deserializing objects in NOF (Newspeak Object Format).
Again, it could be done otherwise, but its a lot easier this way.

>
>
> > > > A correct implementation of  doesNotUnderstand: is necessary as well.
>  I
> > > > understand some people on the list are looking at these issues.
> >
> > > What's wrong with Strongtalk's #doesNotUnderstand:?
> >
> > It doesn't seem to get called if you override it.
>
> So, Strongtalk's polymorphism breaks on #doesNotUnderstand:, but not
> in general (seems to be working everywhere else in the image?).


talksmall explained the mechanics in detail.  Bottom line. It does not work
as expected.

>
>
>


-- 
Cheers, Gilad

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---