Nice to see it still going. For those unaware, Squeak linage descends directly from the last Xerox Smalltalk-80 images before being bootstraped.
Smalltalk Squeak 6.0
11–20 of 73 posts
Re: Smalltalk Squeak 6.0
#12Could a developer use Squeak as an emacs replacement?
Re: Smalltalk Squeak 6.0
#13Could a developer use Squeak as an emacs replacement?
Re: Smalltalk Squeak 6.0
#14Could a developer use Squeak as an emacs replacement?
He shipped enterprise code this way. Implementation language was Perl.
Re: Smalltalk Squeak 6.0
#15Nice to see it still going. For those unaware, Squeak linage descends directly from the last Xerox Smalltalk-80 images before being bootstraped.
Don't know if it's true, but it makes a fun story: ST80 used reference counting with counts saturating at some low number (like 127), and of course there are problems collecting circular references. A comprehensive analysis of a modern image, with Xerox PARC lineage, discovered garbage that had been uncollected for 20-30 years.
There are two zombie processes (OID 6662 and 19ba). There are also a couple of BlockContext and MethodContext which have a nil sender and a reference to an unknown method, but which are still referenced from somewhere (i.e. the collection is prevented, even with mark & sweep). E.g. OID 79a2 of class BinaryChoice. I have a full list if anybody is interested.
Re: Smalltalk Squeak 6.0
#16Re: Smalltalk Squeak 6.0
#17Could a developer use Squeak as an emacs replacement?
I once worked with a guy who did all his coding in Squeak the way some do in Emacs. He shipped enterprise code this way. Implementation language was Perl.
Re: Smalltalk Squeak 6.0
#18Re: Smalltalk Squeak 6.0
#19Could a developer use Squeak as an emacs replacement?