Re: 3.0 merge status (observations and a code variant)

Using a vanilla Pharo 11.4 install as recommended today at the pharo downloads page with the Seaside.st mcm file all looks to be going well until methods begin to recompile late in the load: the image is 60 MB and Pharo.exe simply consumes the available CPU cycles but the working memory size stays fixed. After 15 - 20 minutes I conclude that it is dead (the UI is unresponsive) and kill it with Process Explorer. There is no busy cursor, no visible message box, no minimized msg box at the bottom. Nothing new gets logged. I would say it was very close to being done given what is in the frozen view of the Monticello browser ... The last change written to .changes was this: RBAssignmentNode removeSelector: #assignmentPosition! !RBLiteralNode commentStamp: 'md 8/9/2005 14:58' prior: 34068596! RBLiteralNode is an AST node that represents literals (e.g., #foo, #(1 2 3), true, etc.). Instance Variables: token <RBLiteralToken> the token that contains the literal value as well as its source positions ! !RBLiteralNode commentStamp: 'md 8/9/2005 14:58' prior: 40424826! RBLiteralNode is an AST node that represents literals (e.g., #foo, #(1 2 3), true, etc.). Instance Variables: token <RBLiteralToken> the token that contains the literal value as well as its source positions ! --- On Sat, 1/9/10, Lukas Renggli &lt;renggli(a)gmail.com&gt; wrote: