- Pharo-dev - lists.pharo.org

Assigning to Block and Method arguments
by Marcus Denker Oct. 8, 2014

Oct. 8, 2014

Hi, In Pharo3 we had the bug that assigning to method arguments was allowed. *Block* arguments are traditionally assignable, but this is equally a bad idea (there was already a setting to forbid it, but no idea how to make it a default without making a lot of code unlovable). First we made method arg assignment in Pharo4 an error, like it was in Pharo2, but the problem with that is that there is code out there alreadyâ¦ so (thanks to Nicolai Hess), now assignments to method arguments raise an error in interactive mode (when coding), but load fine e.g. with Monticello. Yesterday I extended that scheme to block arguments: Now block argument assignments are forbidden in interactive mode, while legacy code loads fine. (I removed the #allowBlockArgumentAssignment setting, too). This way we have a good transition and in some versions can make raising errors on assignments to arguments the default even in non-interactive mode. Marcus

4 4

Re: [Pharo-dev] FOSDEM > Looks like there is a Smalltalk room :)
by Stephan Eggermont Oct. 8, 2014

Oct. 8, 2014

Yes, I'll put the CFP out soon. Stephan

2 1

Someone remember a video ?
by Serge Stinckwich Oct. 7, 2014

Oct. 7, 2014

I remember someone (Stef ?) send a link to a video demo in the mailing-list about a framework in order to verify lively that an object is initialized correctly. Everytime you send a message to a new object, there was a report about uninitialized properties. Anyone remember about this work ? Thank you. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Help fight Ebola by joining the Computing for Ebola Challenge http://bit.ly/1oEdBag

3 2

GT-Inspectors need live updating
by Sven Van Caekenberghe Oct. 7, 2014

Oct. 7, 2014

It seems that currently there is no automatic live updating for GT-Inspectors. That has to be fixed since we had that in both the old and in the eye inspectors. I remember Stef did something to do this with an extra process. Sven

4 11

FOSDEM > Looks like there is a Smalltalk room :)
by phil＠highoctane.be Oct. 7, 2014

Oct. 7, 2014

https://fosdem.org/2015/news/2014-09-30-accepted-devrooms/ Phil

1 0

[pharo-project/pharo-core] 540247: 40287
by GitHub Oct. 7, 2014

Oct. 7, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 540247e6a0a41db6b7409810838453d45c3e4995 https://github.com/pharo-project/pharo-core/commit/540247e6a0a41db6b7409810… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-07 (Tue, 07 Oct 2014) Changed paths: A Deprecated40.package/extension/MorphicUIManager/instance/request_initialAnswer_centerAt_.st A Deprecated40.package/extension/NonInteractiveUIManager/instance/request_initialAnswer_centerAt_.st A Deprecated40.package/extension/UIManager/instance/displayProgress_at_from_to_during_.st A Deprecated40.package/extension/UIManager/instance/request_initialAnswer_centerAt_.st M Morphic-Widgets-Tree.package/MorphTreeModel.class/instance/announcing/on_send_to_.st M Morphic-Widgets-Tree.package/MorphTreeMorph.class/instance/announce requests/registerRequestHandlers.st M OpalCompiler-Core.package/AbstractCompiler.class/class/settings/compilerSettingsOn_.st R OpalCompiler-Core.package/CCompilationContext.class/class/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/CompilationContext.class/class/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/CompilationContext.class/class/accessing/allowBlockArgumentAssignment_.st M OpalCompiler-Core.package/CompilationContext.class/definition.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/variables/checkVariableIsWritable_.st M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/variables/lookupVariableForWrite_.st R Polymorph-Widgets.package/MorphicUIManager.class/instance/ui requests/request_initialAnswer_centerAt_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script287.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40287.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R UIManager.package/NonInteractiveUIManager.class/instance/ui requests/request_initialAnswer_centerAt_.st R UIManager.package/UIManager.class/instance/deprecated/displayProgress_at_from_to_during_.st R UIManager.package/UIManager.class/instance/deprecated/request_initialAnswer_centerAt_.st Log Message: ----------- 40287 14179 deprecate the method in UIManager "deprecated" category https://pharo.fogbugz.com/f/cases/14179 14162 Replace Announcer>>#on:send:to:s senders in Morphic-Widgets-Tree https://pharo.fogbugz.com/f/cases/14162 14173 remove #allowBlockArgumentAssignment preference https://pharo.fogbugz.com/f/cases/14173 http://files.pharo.org/image/40/40287.zip

1 0

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

Oct. 7, 2014

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

1 0

WhatsUp from: 2014-10-06 until: 2014-10-19
by seaside＠rmod.lille.inria.fr Oct. 7, 2014

Oct. 7, 2014

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-10-19 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

9 10

gt issues
by Tudor Girba Oct. 7, 2014

Oct. 7, 2014

Hi, >From the feedback so far, I could not the following issues: - menus for copy/paste/cut (which I still wonder why they need to exist for a developer, but we will add them) - possibility of save/open - Cmd+g instead of Cmd+o (already fixed) - position of the cursor is sometimes messed up - possibility to change the title of the Playground - possibility to group the windows (this will likely not be fixed in the same way) (did I miss any?) - icons and text background are not ready for the dark theme Did I miss anything? Could the people that want to see any of these issues done open tickets for them? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 24

DNUs in the styler
by Thierry Goubier Oct. 7, 2014

Oct. 7, 2014

I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well? A way to reproduce: RBParser parseFaultyMethod: 'test ^ ()' Whereas: RBParser parseFaultyMethod: 'test ^ ^ self' correctly returns an AST with RBParseErrorNode(s) inside. Thierry

3 5