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

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Shaping
> Sent: Thursday, May 22, 2008 8:15 PM
> To: Strongtalk-general
> Subject: Re: Status of Strongtalk C++ code: VM stability and progress on
> a graphical debugger
>
>
>
> On May 21, 4:03 am, talksmall <[email protected]> wrote:
>
> > > Do we have a standard set of test-scripts in Smalltalk (SUnit tests or
> > > even an agreed upon DoIt or set of them) that drill the VM for various
> > > basic functions, as well as new ones being tested for the first time,
> > > like your ANSI exception handling?  In each test cycle I want to know
> > > that I'm fixing my own stuff and not breaking someone else's.
> >
> > There are some Smalltalk-side tests, but very little at the level of
> > the VM itself. If you look at Bootstrap>>deterministicallyTestSystem,
> > this is the closest to a SUnit test suite. Actually, now that my
> > exception handling stuff is nearly complete, I managed to port across
> > SUnit from the Squeak version, so we could port these across to a
> > separate set of test classes, as well as adding our own, as they are a
> > bit skimpy. I have never liked the idea of having the test code for a
> > class within the class itself.
> >
> > There is a handy little test script that can be used to run this
> > automatically from the command line within starting the UI. You will
> > find it in tools/test.dlt. To run this use something like
> > strongtalk_debug.exe -f tools\strongtalkrc-forInterpretedTests -script
> > tools\test.dlt from the strongtalk directory.
> >
> > BTW once you manage to build strongtalk, and assuming that you are
> > using the gcc-linux branch, you will need a compatible image and
> > sources. You can find a zip containing these on the downloads page of
> > the wiki. You should unzip them in the strongtalk directory.
> >
> Why do we not place the compatible image and sources with the source
> code?  How is the image created or changed when necessary?

There are two issues: first, Subversion is not suitable for archiving large
binary files (and there is only a 100MB limit on the archive).  Secondly, we
cannot yet rebootstrap the image, so we always need to start with a working
image.  But that won't be that hard to fix.  Once we can re-bootstrap,
having the image is no longer necessary, it just acts as a convenient cache.
-Dave

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