I agree with Igor.  Slang is a powerful concept that has helped Squeak a lot.

On 10/31/07, Igor Stasenko <siguctua at gmail.com> wrote:
> On 31/10/2007, Rob Withers <reefedjib at yahoo.com> wrote:
> >
> > ----- Original Message -----
> > From: "Igor Stasenko" <siguctua at gmail.com>
> > To: "The general-purpose Squeak developers list"
> > <squeak-dev at lists.squeakfoundation.org>
> > Sent: Wednesday, October 31, 2007 9:39 AM
> > Subject: Re: Thoughts on a concurrent Squeak VM (was: Re: Concurrent
> > Futures)
> >
> >
> > > On 31/10/2007, Rob Withers <reefedjib at yahoo.com> wrote:
> > >> Andreas,
> > >>
> > >> What about using C++?  There would be some degradation of performance.
> > >> However, there would be the benefit of structuring the VM classes, of not
> > >> having to add VM as an argument everywhere, and it may even be possible
> > >> to
> > >> subclass Thread so we know where the thread-local storage is.
> > >>
> > > I'd rather prefer to make modifications to slang to be able to
> > > generate VM sources for any target language/platform and keep platform
> > > dependent code in image instead in separate file(s). This all to
> > > simplify build process and to keep all things together.
> >
> > You mean subclassing a Thread class?  Is that platform dependent?  If so, I
> > didn't know that and I agree with you - it's should be out in a separate
> > file, if used at all.
> >
> No, i mean to keep ALL plugins code in corresponding methods, and
> never use external sources.
> For example, a SocketPlugin can have subclasses Win32SocketPlugin,
> UnixSocketPlugin
> and in these subclasses we should keep a code for different platforms.
> But not in .c sources.
>
> > cheers,
> > Rob
> >
> >
> >
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
>