- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Oct. 22, 2014

Oct. 22, 2014

Branch: refs/tags/40320 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 616625: 40320
by GitHub Oct. 22, 2014

Oct. 22, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 61662547acfd2442545be7c8734b8ef2a7355d5b https://github.com/pharo-project/pharo-core/commit/61662547acfd2442545be7c8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-22 (Wed, 22 Oct 2014) Changed paths: A KernelTests.package/MethodContextTest.class/instance/tests - ast mapping/testSourceNodeOptimizedBlock.st M OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/initialize/irPrimitive_.st M OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/results/compiledMethodWith_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script320.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40320.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40320 14286 add a test for #sourceNode on Contexts for optimized blocks https://pharo.fogbugz.com/f/cases/14286 14283 Slice for Spur integration https://pharo.fogbugz.com/f/cases/14283 http://files.pharo.org/image/40/40320.zip

1 0

Thanks vonBecman :) and BernardoContreras
by stepharo Oct. 22, 2014

Oct. 22, 2014

Hi guys I want to thank Bernardo because he is the simple example of helping on simple issues that we love to fix but do not have the time because running on urgent ones. Bernardo fixed the complete system package by package, one after the other in this tedious and steady matter and he step by step (let us repeat again) changed all the on:do: annoucememt senders into when:do:. You could think Oh this is easy and not important. It is important. Such systematic actions improve the system! THANKS BERNARDO! Stef PS: I want to THANK NICOLAI HESSE and SVEN for their spirit. You all give me the energy to push.

1 0

ProtoObject/Proxies
by Esteban A. Maringolo Oct. 22, 2014

Oct. 22, 2014

I've been hit by a few side effects of using proxies (GLORP ones), because some tools like the Debugger and/or inspectors expect some objects to respond to methods not defined in ProtoObject. I discovered this by accident because looking at the stack in the xterm console I saw a recursion triggered by a halt in UnitOfWork>>#register: Such halt caused errors that needed to be printed, and because it was trigger in the context of a Proxy, boom, infinite recursion. Why such methods are not implemented in ProtoObject, or at least with a "basic" version of it. Is this by design? Methods like #shouldBePrintedAsLiteral or #isSelfEvaluating (don't know what it means), along others like #printStringLimitedTo... etc. I remember Steph said a better support for Proxies was in the was roadmap, how far is that? What can be done to speed this up? Debugging a proxy object (even one that doesn't use #become:) is really tricky. If you look at the implementation of Glorp's Proxy>>#class it seems it should answer the class of the proxied object (if materialized), but all that is commented out returning the receiver class, it is returning Proxy. If you uncomment that weird things happen. I'll come back to this later, once I have time to reproduce it. Please don't forget not everything inherits from Object :) Esteban A. Maringolo

4 8

Smalltalk running on Dart VM?
by askoh Oct. 22, 2014

Oct. 22, 2014

Dart is climbing in popularity. And Dart VM is going to be built into Chrome. Would it be advantageous to run Smalltalk on the Dart VM ? Since Dart is very Smalltalk like, wouldn't it be relatively easy? Thanks, Aik-Siong Koh -- View this message in context: http://forum.world.st/Smalltalk-running-on-Dart-VM-tp4785841.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 3

[pharo-project/pharo-core] 66e5ed: 40319
by GitHub Oct. 22, 2014

Oct. 22, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 66e5edb2b85fb05122b7162a3e4648447325ee0d https://github.com/pharo-project/pharo-core/commit/66e5edb2b85fb05122b7162a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-22 (Wed, 22 Oct 2014) Changed paths: A KernelTests.package/BlockClosureTest.class/instance/tests - astmapping/testSourceNodeOptimized.st A OpalCompiler-Core.package/IRSequence.class/instance/inspector/sourceNode.st M OpalCompiler-Core.package/extension/BlockClosure/instance/sourceNode.st A OpalTools.package/extension/IRInstruction/instance/gtInspectorTreeIn_.st A OpalTools.package/extension/IRSequence/instance/gtInspectorTreeIn_.st A OpalTools.package/extension/SymbolicBytecode/instance/gtInspectorTreeIn_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script319.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40319.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40319 14284 fix #sourceNode for Blocks https://pharo.fogbugz.com/f/cases/14284 14282 add SourceNode tab for IRInstruction and SymbolicBytecode https://pharo.fogbugz.com/f/cases/14282 http://files.pharo.org/image/40/40319.zip

1 0

[pharo-project/pharo-core]
by GitHub Oct. 22, 2014

Oct. 22, 2014

Branch: refs/tags/40319 Home: https://github.com/pharo-project/pharo-core

1 0

BlockClosure source code
by Jan KurÅ¡ Oct. 22, 2014

Oct. 22, 2014

Hi, I need to extract a source code from a block closure and I found something strange: [ :ctx | [ ctx atEnd ] ifTrue: [ ] ] . [ :ctx | [ ctx atEnd ] whileTrue:[ ] ]. Print of the first line returns: '[ :ctx | [ ctx atEnd ] ifTrue: [ ] ]' Print of the second line returns: '[ ctx atEnd ]' And honestly, I have no idea why. This behaviour was observed in Pharo3 and Pharo4. Is there a way how to get a consistent result, i.e. '[ :ctx | [ ctx atEnd ] whileTrue:[ ] ]' for a second line? Thank you in advance! Jan

8 15

[Pharo4] inspector shows the ASTNode that generated a Bytecode
by Marcus Denker Oct. 22, 2014

Oct. 22, 2014

Small extension: This way one can quickly see which AST node the system thinks corresponds to which byte code. I added this for Bytecodes and the Opal IR. (this should show the whole AST and just highlight the partsâ¦ later) Â Â Â Marcus

2 1

[pharo-project/pharo-core]
by GitHub Oct. 22, 2014

Oct. 22, 2014

Branch: refs/tags/40318 Home: https://github.com/pharo-project/pharo-core

1 0