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

God, I'm glad I found this forum. I have been hand-porting the Windows
source to Ubuntu using the Anjuta IDE to help create the make files
and dependencies and I was pulling my hair out.I'll get the code from
svn.

A general question: Is anyone preparing to offer commercial support
for this ? To ever get serious consideration companies will have to
believe that there is an organization behind Strongtalk.

On Mar 4, 3:36 am, talksmall <[email protected]> wrote:
> You will find the most recent instructions for building the code on
> the Wiki -http://code.google.com/p/strongtalk/wiki/Building. I have
> only used VC++ 2K5 Express to build under Windows. You can ignore the
> part of the instructions that refer to the assembler sources and
> the .obj files. These are no longer required. prunedtree has ported
> the assembler code to the built-in macro assembler within the
> Strongtalk binary. One of the first things the VM does on start up is
> to generate the code for the interpreter and stub routines that used
> to be written in assembler.
>
> As for a project file, I don't do much work in Windows; my interest is
> in the Linux port. When I do some work in Windows I have tended to
> construct the project file from scratch.
>
> I would suggest working with the gcc-linux branch. Although, as it's
> name suggests, it is the home of the Linux port, I have made efforts
> to ensure that the code continues to run under Windows as well. In
> order to use this you will need a copy of a compatible image and
> sources. These can be found on the download page of the Wiki -http://code.google.com/p/strongtalk/downloads/list. This image can be
> used by both the Windows and Linux versions of the VM.
>
> As to VM stability, the interpreter appears to be reasonably stable.
> The recompiler is another matter, at least under Linux. Since so
> little of the code is OS dependent, I imagine the story is probably
> quite similar under Windows, but I haven't really tested that
> assumption. Most of the issues I have seen appear to be related to non-
> local returns from blocks (I discovered this while writing a pure
> Smalltalk implementation of ANSI exception handling that relies
> heavily on NLRs).
>
> Regards, talksmall
>
> On Mar 4, 7:04 am, Shaping <[email protected]> wrote:
>
> > This link seems to refer to a build involving Assembler. I thought
> > that all of this was recently removed and converted to C++.
>
> > Shaping
>
> > On Mar 3, 10:34 pm, "Krzysztof Kowalczyk" <[email protected]>
> > wrote:
>
> > > On Mon, Mar 3, 2008 at 7:30 PM, Shaping <[email protected]> wrote:
> > > >  What about a complete procedure for building from the latest C++
> > > >  (pure) source?
>
> > > Pretty detailed instructions are in the source code:
>
> > >http://code.google.com/p/strongtalk/source/browse/trunk/README.txt
>
> > >-- kjk
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---