- Pharo-dev - lists.pharo.org

Last Pharo VM on mac os x 10.6.8
by Serge Stinckwich Sept. 10, 2014

Sept. 10, 2014

Dear all, a guy in my lab try to use the last version of MOOSE 5.0 (last Pharo VM version) on mac os x 10.6.8. Apparently ROASSAL examples does not work (Cairo library problems). Do we have to upgrade his machine to the last mac os x version ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1

latex exporter in Pillar
by Alexandre Bergel Sept. 10, 2014

Sept. 10, 2014

Hi! I am currently investigating whether Pillar may be used for the AgileVisualization book. I am interested in exporting to PDF and Latex. I have tried the command: ./pillar export âto=latex first.pier > first.tex But the generated .tex file is not valid since it contains a line: -=-=-=-= \newcommand{\ct}[1]} -=-=-=-= Will this be fixed ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 12

Problem with Roassal examples Composite shapes
by kilon alios Sept. 10, 2014

Sept. 10, 2014

So I was browsing the examples for Roassal 2 that I installed in Pharo 3 and I took a look at Composite Shapes category I tried to view the examples and they all look like the attached image Why ? Am I missing a library or something ? â

2 2

OrderedCollection protocols are broken: a potential fix
by ClÃ©ment Bera Sept. 10, 2014

Sept. 10, 2014

Hello guys, I was looking into the OrderedCollection protocols recently to see how well the sista optimizer perform with it methods, and I realized that this is completely broken. For example: col := #(1 2 3 4 5) asOrderedCollection. col do: [ :elem | elem trace . elem < 4 ifTrue: [ col add: col size + 1 ]]. => '12345678' However: col := #(1 2 3 4 5) asOrderedCollection. col collect: [ :elem | elem trace . elem < 4 ifTrue: [ col add: col size + 1 ]]. => '12345' This means that #do: and #reverseDo: iterate over all the elements of the collection,*including* the ones that you are adding while iterating over the collection, whereas all the other OrderedCollection protocols, such as #collect:, #select:, iterates over all the elements of the collection, *excluding* the ones you are adding while iterating over the collection. Marcus argued that one should not edit a collection while iterating over it, however this point is not valid as the World menu relies on this feature, using #do: to iterate over the elements of the OrderedCollection including the one it is adding while iterating over the collection. Changing the implementation makes the world menu display half of its items. I don't like this difference because it is inconsistent. For example, refactoring a #do: into a #collect: can simply not work because they do not iterate over the same elements if you are editing the collection while iterating over it. In VW, the protocols are consistent and iterating over a collection never iterates over the elements one is adding while iterating over it. Therefore, I believe most frameworks should expect this behavior (at least the ones cross smalltalk) which sounds the most correct. I think we should fix the world menu implementation and make the protocols consistent. Alternatively, we can let VW be a much more consistent Smalltalk environment than Pharo. What do you think ? Clement

10 17

[pharo-project/pharo-core]
by GitHub Sept. 10, 2014

Sept. 10, 2014

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

1 0

from time to time I get a crash when increasing the main window size
by stepharo Sept. 10, 2014

Sept. 10, 2014

basicNew value: new: replaceFrom:to:with:startingAt: new: basicNew new: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: value: primShowRectLeft:right:top:bottom: value: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: primShowRectLeft:right:top:bottom: I will try to reproduce it.

3 2

Adding new shortcuts - reset of KMRepository?
by phil＠highoctane.be Sept. 10, 2014

Sept. 10, 2014

I wanted to add some new global shortcuts but now, how to get these taken into account? Doing KMRepository reset doesn't seems the right way to go. ? TIA Phil

1 0

[pharo-project/pharo-core] da7050: 40216
by GitHub Sept. 10, 2014

Sept. 10, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: da70500fab822af929ba9ae3f26d4f2ddd015918 https://github.com/pharo-project/pharo-core/commit/da70500fab822af929ba9ae3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-10 (Wed, 10 Sep 2014) Changed paths: M Collections-Sequenceable.package/LinkedList.class/instance/adding/add_after_.st M Collections-Sequenceable.package/LinkedList.class/instance/adding/add_before_.st M Collections-Strings.package/ByteString.class/class/initialization/initialize.st M MenuRegistration.package/PragmaMenuAndShortcutRegistration.class/instance/menu protocol/with_.st M MenuRegistration.package/PragmaMenuBuilder.class/instance/private/interpretRegistration_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script216.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40216.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40216 13979 PragmaMenuBuilder relies on modifying a collection while iterating over it. https://pharo.fogbugz.com/f/cases/13979 13983 Temporary variables not read AND written in LinkedList https://pharo.fogbugz.com/f/cases/13983 13984 Temporary variables not read and written in ByteString class>>#initialize https://pharo.fogbugz.com/f/cases/13984 http://files.pharo.org/image/40/40216.zip

1 0

[pharo-project/pharo-core]
by GitHub Sept. 10, 2014

Sept. 10, 2014

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

1 0

New Cog VMs available
by Eliot Miranda Sept. 9, 2014

Sept. 9, 2014

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3072. CogVM binaries as per VMMaker.oscog-eem.876/r3072 Fix bad regression in FilePlugin>>primitiveFileSetPosition introduces around r2797 that breaks > 1Gb file access. Change manifest files on Windows to make app HIGHDPIAWARE. Create a manifest for the consolevm and include it in the archive. Fix bug with become where duplicate entries in the input array would crash the system (thanks Igor). Make nameOfClass: more robust, in both the real and simulated VMs. Regenerate sources after refactoring Slang code to ask classes what methods they want to include based on their initializationOptions inst var instead of the centralized VMMaker. Generate Spur Newspeak VMs with the new CompiledMethod header format. This will break the Newspeak Spur bootstrap until NOF generation and/or loading is fixed. -- best, Eliot

1 1