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

Hi.

> > To continue working with Strongtalk, as if it were a serious tool and
> > not a cool toy, I need:  stability, a graphical debugger, external
> > interfacing to DDLs, and then a sound concurrency model.
>
> Stability is the hard part, where one needs a detailed understanding of the
> VM code.  As I've said, getting a full debugger isn't that hard:
>
> I'm not sure  what you mean by "DDL"? Data Definition Language? Or is it a
> typo?

Yes, typo:  Should be "DLLs"

 In any case, you can call out to C and have C call back via the FFI
> and do whatever.

Great.


> I expect actors on top of the current system would satisfy your concurrency
> needs.

I think so.

> >  When I arranged for Strongtalk's release at Sun I
> > > had hoped the open source community would make it robust enough for real
> > > use. So far, progress has been rather slow. I hope that will change.
>
> > We need to understand why the progress has been slow.  Strongtalk
> > looks like advanced compiler technology to me.  Why aren't people
> > working on it?  Is the C++ code difficult to understand?  Is it badly
> > organized?
>
> It is very well organized, but it is still difficult to understand, because
> high performance VMs are difficult to understand.

I don't see why the understanding would be difficult to achieve with
modular, well factored code, but I haven't actually looked at any of
it yet.


Shaping
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---