Smalltalk Squeak 6.0

Post by Rochus » Thu, Jul 07, 2022, 12:09 AM UTC

igouy wrote: post #39

Rochus wrote: post #15

Earlier quoted context omitted.

It is true, that there is uncollected garbage in the original Xerox ST80 image. I've built some tools to analyze the image and also a VM which can be interrupted at any time to analyze the current state of the image (see https://github.com/rochus-keller/Smalltalk ). 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…

Is there uncollected garbage in the Smalltalk Squeak 6.0 image?

Post by protomyth » Thu, Jul 07, 2022, 1:09 AM UTC

Qem wrote: post #9

> Switches the default bytecode set to SistaV1. This lays the basis for a new generation of VM optimizations (Sista: Speculative Inlining Smalltalk Architecture). With Sista, blocks are represented by CompiledBlocks and instantiated as FullBlockClosures, the stability of which has been improved in the course of this switch (fixed bugs in FullBlockClosure >> #= and InstructionStream >> #scanForInstructionSequence:). P…

Post by pjmlp » Thu, Jul 07, 2022, 5:53 AM UTC

Rochus wrote: post #42

igouy wrote: post #40

Earlier quoted context omitted.

For some meaning of "contain things it shouldn't": Given that the base image we started working with didn't "contain things it shouldn't" why could we not be completely sure that base image + source code fileIn didn't "contain things it shouldn't" ?

First, as most other companies using ST we were not working on the original image, but on a company-specific one that had been in use for a long time and contained a lot of company-specific stuff. On the other hand, there were also things in the original images of the commercial STs that one would or should not ship with the product.

Post by Rochus » Thu, Jul 07, 2022, 9:55 AM UTC

pjmlp wrote: post #45

Rochus wrote: post #42

Earlier quoted context omitted.

First, as most other companies using ST we were not working on the original image, but on a company-specific one that had been in use for a long time and contained a lot of company-specific stuff. On the other hand, there were also things in the original images of the commercial STs that one would or should not ship with the product.

Which is why image trimming tools did exist.

Post by 7thaccount » Thu, Jul 07, 2022, 4:38 PM UTC

whartung wrote: post #35

bitwize wrote: post #29

Earlier quoted context omitted.

Presumably he could write his own code- and data-munging tools in Smalltalk and invoke them straight from the running image -- kinda like what you can do with Emacs Lisp.

That's fascinating. At least Emacs comes with an editor, can't say as much for Squeak. I mean, it has AN editor, its just not very good compared to something like Emacs or vi, and I'm talking editor functionality, not everything else. It's more like a lightly enhanced Text Area. But maybe he put a lot of work into it to be a better Perl editor.