RE: proposal for how to synchronize Strongtalk source

"SmallSqueak" <[email protected]> Thu, 10 May 2007 14:47:31 -0400
Newsgroups gmane.comp.lang.smalltalk.strongtalk
Message-ID <00a901c79333$aac2b250$004816f0$@com>


> -----Original Message-----
> From: [email protected] [mailto:strongtalk-
> [email protected]] On Behalf Of David Griswold
> Sent: Wednesday, May 09, 2007 11:51 AM
> To: [email protected]
> Subject: RE: proposal for how to synchronize Strongtalk source
> 
> 
> 
> 
> > -----Original Message-----
> > From:  SmallSqueak
> > Sent: Thursday, May 10, 2007 4:07 PM
> > To: [email protected]
> > Subject: RE: proposal for how to synchronize Strongtalk source
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]] On Behalf Of
> > > David Griswold
> > > Sent: Wednesday, May 09, 2007 5:21 AM
> > > To: [email protected]
> > > Subject: RE: proposal for how to synchronize Strongtalk source
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From:  SmallSqueak
> > > > Hi Dave,
> > > >
> > > > 	I am looking at the contents of the archive
> > > > 	"sources folder for bootstrapping(must unpack).zip"
> > > >
> > > > 	There are 3 log files:
> > > >
> > > > 	1/- strongtalkchange.log (7,796KB 10/17/2006 1:40PM)
> > > > 	2/- strongtalSave.log (1KB 10/17/2006 1;40PM)
> > > > 	3/- strongtalkrestore.log (0KB 10/17/2006 1:27PM)
> > > >
> > > > 	1 id file "strongtalksource.id" (1KB 10/17/2006 1:40PM)
> > > >
> > > > 	836 .class files
> > > > 	963 no-extension files
> > > >
> > > > 	Most of the no-extension files have a corresponding file.
> > > >
> > > > 	Would you please explain the relationship between these
> files,
> > > > 	and what does it mean when a no-extension file does not
> have
> > > > 	.class counterpart.
> > > >
> > > > 	What can one do with these files if there is available
> > > a bootstrap
> > > > 	image (built from what?) and a latest and greatest VM.
> > >
> > > Nothing.  That zip file contains a snapshot of the Strongtalk
> > > source code internal directory structure, just so we don't
> > > lose it.
> >
> > 	I am asking this because I noted that when I tried to
> > 	"Recompile world..." from the Strongtalk Launcher File menu,
> > 	I got this from the command prompt console:
> >
> >
> > Smalltalk Virtual Machine by LongView Technologies LLC
> > ---------------------------------------------------------
> > (c) 1994-1997 Sun Microsystems, Inc. ALL RIGHTS RESERVED.
> > Use and distribution of this software is subject to the
> > terms of the attached license.
> > ---------------------------------------------------------
> > Version 1.1 (build May  8 2007 19:31:42)
> > (use argument -? for a list of flags)
> >
> > [Reading in strongtalk.bst, n, 0.365 secs]
> > Recompiling DeltaPolyProtocolMsgSignature
> >
> > 	and an "Error: This shouldn't happen" at "MixinSourceHandler
> > 	on
> DeltaPolyProtocolMsgSignature>>sourceForSelector:#'visibility'"
> >
> > 	"sources folder for bootstrapping(must unpack).zip"
> > 	was unpacked and "Recompile world..." looked like this:
> 
> It sounds to me like you haven't actually downloaded and installed the
> current Strongtalk release.  You can't construct a working system just
> from
> the repository right now, you need to start from the binary release,
> which
> will set up your source directory etc first.  The repository is only
> used
> for building the VM executable right now.  The image and source
> directory
> etc must come from the release.
> 
> >
> > Smalltalk Virtual Machine by LongView Technologies LLC
> > ---------------------------------------------------------
> > (c) 1994-1997 Sun Microsystems, Inc. ALL RIGHTS RESERVED.
> > Use and distribution of this software is subject to the
> > terms of the attached license.
> > ---------------------------------------------------------
> > Version 1.1 (build May  8 2007 19:31:42)
> > (use argument -? for a list of flags)
> >
> > [Reading in strongtalk.bst, n, 0.371 secs]
> > Recompiling DeltaPolyProtocolMsgSignature
> > [...]
> > Recompiling ProtocolOutliner class
> > Recompiling Bootstrap
> >
> > 	and an "Error: This shouldn't happen" at "MixinSourceHandler
> > 	on Bootstrap>>sourceForSelector:#'deterministicallyTestSystem'"
> >
> > 	Where does this sequence of filing in come from? I looked at
> various
> > 	.gr files and cannot find any of them fitting the above sequence.
> 
> That is not filing in, that is recompiling the methods in the image
> from the
> source in the source database, not from the original source code.  It
> is
> happening in hash order.
> 
> > 	BTW, how can I copy the contents of "Error: This shouldn't
> happen"
> > 	for reporting purpose later on (I am aware that these errors are
> due
> >
> > 	to the source synchronizing problem).
> >
> > > It is not something you generally play around with.
> > >
> >
> > 	But is crucial for building a new image, isn't it?
> 
> As I've said, you *cannot* bootstrap a new image right now.
> 
> >
> > > That zip file contains a snapshot of the Strongtalk
> > > source code internal directory structure
> >
> > 	It is much appreciated if you would elaborate.
> >
> > 	A good understanding of the infra structure would
> > 	take a Strongtalk learner a long way.
> 
> The zip file is just a copy of the 'source' subdirectory from the
> original
> binary release.  It is only there for archival purposes.  If you want
> to
> look at it, install the binary release, which you must do first anyway,
> and
> look at the 'source' directory.
> 
> It sounds like perhaps the documentation isn't clear enough about
> having to
> install the binary release to get a running system, regardless of
> building
> the VM.  I'll make a note to clarify the documentation.
> 
> -Dave
> 

	Sorry again, but I cannot find anything to download from here:

	http://code.google.com/p/strongtalk/downloads/list

	Where can I download the latest release?

	Thanks,

	PhiHo



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