- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Dec. 21, 2016

Dec. 21, 2016

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

1 0

a request to change the meaning of <example> pragma
by Tudor Girba Dec. 21, 2016

Dec. 21, 2016

Hi, As you might know, a while ago we created GTExamples, a framework that supports both example-based live documentation and testing: http://gtoolkit.org/doc/Examples/examples.html GTExamples was part of the GTInspector for a while, but as it evolved, we pulled it out in a separate project. This separate project is not in Pharo anymore but it is part of the full GToolkit configuration (Pharo only ships the core of GToolkit). The idea of taking GTExamples out was to allow the community to have a more elaborate discussion about the role of examples in our environment. I have invited you to join that conversation, but it did not take off. I understand that perhaps the topic does not look appealing at this moment. We will certainly continue to evolve GTExamples both on the semantics level of the dependency constructs and on the integration with tools. Our goal is to enable a new practice that I would like to call Example-Guilded Development (or Example-Driven Development), and position Pharo to be the only platform on which someone can do that. But, that is our goal, and does not have to be the same with other peopleâs goal. Right now, GTExamples relies on the <gtExample> pragma to denote a method that returns an object that exemplifies something. Executing this method as an example should have no side-effects (either because the method itself does not have a side-effect, or because the example method defines how the cleanup should happen using the mechanism provided by GTExamples). This meaning is different from the meaning of the <example> pragma used through Pharo. There are currently 55 places that use this pragma inside Pharo and most of them come from FastTable. As things will progress and more libraries might use GTExamples, the situation can become confusing. To make things less confusing in the future, I would like to define the meaning of the <example> to denote a method that returns an object without having side effects. Would you agree with this? If yes, I would suggest the name of the new pragma that would replace the existing one to include âscriptâ in the name. For example, <sampleScript>. What do you think? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."

9 19

About Fraction and parentheses
by Serge Stinckwich Dec. 20, 2016

Dec. 20, 2016

I have one question about Fraction. When I print a fraction like 1/2 in the Playground I obtain (1/2) and when I inspect I obtain ((1/2)). Why do we need all these parentheses ? I didn't try with a current Pharo 6.0 image, because my bandwidth is quite limited right now (Vietnam). -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

4 5

all black pharo 6.0 window on startup - unresponsive
by Dale Henrichs Dec. 20, 2016

Dec. 20, 2016

Running Ubuntu 14.04 and a fresh download (as of yesterday) when pharo comes up I get an unresponsive and all black window -- I have to kill the process. I have an older download of pharo6.0 that works fine ... Both vms are the same version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016 https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply(a)github.com> Jenkins build #594 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /export/foos1/users/dhenrich/dev/_home/dev/clients/pharo60/pharo-vm/ [default: /export/foos1/users/dhenrich/dev/_home/dev/clients/pharo60/pharo-vm/] .. so there must be something wrong in the image itself ... The image that works is: Latest update: #60265 Not sure how to find out what update I am using, since the GUI isn't functional. Dale

2 3

[pharo-project/pharo-core]
by GitHub Dec. 20, 2016

Dec. 20, 2016

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

1 0

[pharo-project/pharo-core] 86be50: 60332
by GitHub Dec. 20, 2016

Dec. 20, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 86be50c96618776323023836fb3a36754b632cdd https://github.com/pharo-project/pharo-core/commit/86be50c96618776323023836… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-20 (Tue, 20 Dec 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version427_.st M Glamour-FastTable.package/GLMMorphicFTRenderer.class/instance/rendering/render_.st M Glamour-Morphic-Brick.package/GLMAlertBrick.class/instance/scripting/alert_.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-opening/openInBrickWindowLabeled_.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-opening/window.st M Glamour-Morphic-Brick.package/GLMPrivacyAgreementBrick.class/instance/preferences/sendUsageData.st M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/openFromRubric_withResult_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60331.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60332.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60331.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60332.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60332 19480 Update Glamour to version 4.27 https://pharo.fogbugz.com/f/cases/19480 http://files.pharo.org/image/60/60332.zip

1 0

[pharo-project/pharo-core] 37f27a: 60331
by GitHub Dec. 20, 2016

Dec. 20, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 37f27a06b50b8c74abc810d24e3cf9d838dbc413 https://github.com/pharo-project/pharo-core/commit/37f27a06b50b8c74abc810d2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-20 (Tue, 20 Dec 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60330.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60331.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60330.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60331.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60331 18735 DNU on suggestions shortcut in GTDebugger https://pharo.fogbugz.com/f/cases/18735 http://files.pharo.org/image/60/60331.zip

1 0

[pharo-project/pharo-core]
by GitHub Dec. 20, 2016

Dec. 20, 2016

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

1 0

Re: [Pharo-dev] [Moose-dev] Re: Too frequent crashes :-(
by Peter Uhnak Dec. 20, 2016

Dec. 20, 2016

On Mon, Dec 19, 2016 at 08:12:29AM +0800, Ben Coman wrote: > Can yo point to where you added you workaround? The fix is a single line, because I hate myself. interpreterProxy failed ifTrue:[^nil]. https://github.com/pharo-project/pharo-vm/commit/9bf66cf656b176d988e1b0ba74… To give you more info: The problem is that memory of canvas forms are not properly pinned, so during garbage collection the form is being moved, but if at the same time the canvas form is being updated and moved, you are accessing wrong memory -> crash. My fix will return prematurely if an error occurs and throws PrimitiveFailed in the image before any wrong memory is accessed. On Roassal side the PrimitiveFailed is catched and a paint cycle is skipped --- this is good enough, as it results only in ocassional flicker that immediately fixes itself instead of crashing the image. It seems that on Mac there are also other places in the BitBlt code where the surface is being accessed without a check. Also be careful not to be misled by the crash dump stack. It took me quite a while to figure out that GrafPort is already operating on wrong data, so it's not GrafPort's fault, but BitBlt's; of course both should possibly be investigated with respect to the mac crash. Final note, personally I found it much easier the debug and manipulate the resulting C code (and recompiling just that), then to modify the Slang code and rebuild the source code and recompile it all (but again, I don't know what is the proper way to work with the VM code). I used this script to trigger the crash https://gist.github.com/peteruhnak/024650ed2594301558df4da913549b54 As the crash depends on memory consumption and "proper" garbage collection cycle, it wasn't the easiest to reproduce, however the script above usually managed to crash it. Having a more reliable way would be nice, but simply triggering GC (nor full GC) wasn't enough because the memory wasn't in the "right" state. Peter

3 2

[pharo-project/pharo-core] 458c6c: 60330
by GitHub Dec. 19, 2016

Dec. 19, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 458c6cef0678ceeedd886a7e8c952aa72ceddca0 https://github.com/pharo-project/pharo-core/commit/458c6cef0678ceeedd886a7e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-19 (Mon, 19 Dec 2016) Changed paths: M Kernel-Tests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testForMilliseconds.st M Kernel-Tests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testForSeconds.st M Kernel-Tests.package/DelayMillisecondSchedulerTest.class/instance/tests/testForMilliseconds.st M Kernel-Tests.package/DelayMillisecondSchedulerTest.class/instance/tests/testForSeconds.st M Kernel.package/Delay.class/class/initialize-release/initialize.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60329.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60330.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60329.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60330.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A SmartSuggestions.package/SugsAbstractContext.class/instance/accessing/model.st A SmartSuggestions.package/SugsGlamourCodeContext.class/instance/selection/selectTheTextForTheNode.st A SmartSuggestions.package/SugsGlamourCodeContext.class/instance/selection/selectedInterval.st Log Message: ----------- 60330 18735 DNU on suggestions shortcut in GTDebugger https://pharo.fogbugz.com/f/cases/18735 19432 Promote DelaySpinScheduler from experimental status (part 2) https://pharo.fogbugz.com/f/cases/19432 19438 Widen tolerance for DelayScheduler timing tests https://pharo.fogbugz.com/f/cases/19438 http://files.pharo.org/image/60/60330.zip

3 4