- Pharo-dev - lists.pharo.org

Mocketry names again
by Denis Kudriashov May 23, 2016

May 23, 2016

Hi. People start argue that my choice of names are not good. For now Mocketry use "should got" to verify that following message was occurred: mock *should got* someMessage This is broken for native english speakers. Do you agree to replace it with correct #haveReceived? Can we use more short version #haveGot? mock should haveReceived someMessage mock should haveGot someMessage Also there is new expression to verify how object was received during test: result should *beReturnedFrom:* [mock someMessage] Should it be #haveReturnedFrom: ? result should haveReturnedFrom: [mock someMessage] I hope we can make consensus and be happy with Mocketry. Best regards, Denis

6 12

[pharo-project/pharo-core]
by GitHub May 23, 2016

May 23, 2016

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

1 0

[pharo-project/pharo-core] e22bb5: 60028
by GitHub May 23, 2016

May 23, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e22bb56e311438134062dea8f1c80822f144c27c https://github.com/pharo-project/pharo-core/commit/e22bb56e311438134062dea8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-23 (Mon, 23 May 2016) Changed paths: M Collections-Abstract.package/Collection.class/instance/math functions/stdev.st R Kernel.package/Object.class/instance/updating/noteSelectionIndex_for_.st M Morphic-Widgets-Pluggable.package/PluggableListMorph.class/instance/updating/verifyContents.st M Refactoring-Core.package/RBAbstractClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBAbstractInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBAbstractVariablesRefactoring.class/README.md M Refactoring-Core.package/RBAccessorClassRefactoring.class/README.md M Refactoring-Core.package/RBAddClassRefactoring.class/README.md M Refactoring-Core.package/RBAddClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBAddInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBAddMethodRefactoring.class/README.md M Refactoring-Core.package/RBAddParameterRefactoring.class/README.md M Refactoring-Core.package/RBCategoryRegexRefactoring.class/README.md M Refactoring-Core.package/RBChangeMethodNameRefactoring.class/README.md M Refactoring-Core.package/RBChildrenToSiblingsRefactoring.class/README.md M Refactoring-Core.package/RBClassRefactoring.class/README.md M Refactoring-Core.package/RBClassRegexRefactoring.class/README.md M Refactoring-Core.package/RBCreateAccessorsForVariableRefactoring.class/README.md M Refactoring-Core.package/RBExpandReferencedPoolsRefactoring.class/README.md M Refactoring-Core.package/RBExtractMethodRefactoring.class/README.md M Refactoring-Core.package/RBExtractMethodToComponentRefactoring.class/README.md M Refactoring-Core.package/RBExtractToTemporaryRefactoring.class/README.md M Refactoring-Core.package/RBGenerateEqualHashRefactoring.class/README.md M Refactoring-Core.package/RBGeneratePrintStringRefactoring.class/README.md M Refactoring-Core.package/RBInlineAllSendersRefactoring.class/README.md M Refactoring-Core.package/RBInlineMethodFromComponentRefactoring.class/README.md M Refactoring-Core.package/RBInlineMethodRefactoring.class/README.md M Refactoring-Core.package/RBInlineParameterRefactoring.class/README.md M Refactoring-Core.package/RBInlineTemporaryRefactoring.class/README.md M Refactoring-Core.package/RBMethodName.class/README.md M Refactoring-Core.package/RBMethodRefactoring.class/README.md M Refactoring-Core.package/RBMoveMethodRefactoring.class/README.md M Refactoring-Core.package/RBMoveVariableDefinitionRefactoring.class/README.md M Refactoring-Core.package/RBPrettyPrintCodeRefactoring.class/README.md M Refactoring-Core.package/RBProtectInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBProtocolRegexRefactoring.class/README.md M Refactoring-Core.package/RBPullUpClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBPullUpInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBPullUpMethodRefactoring.class/README.md M Refactoring-Core.package/RBPushDownClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBPushDownInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBPushDownMethodRefactoring.class/README.md M Refactoring-Core.package/RBRefactoring.class/README.md M Refactoring-Core.package/RBRefactoringManager.class/README.md M Refactoring-Core.package/RBRefactoryTyper.class/README.md M Refactoring-Core.package/RBRegexRefactoring.class/README.md M Refactoring-Core.package/RBRemoveClassRefactoring.class/README.md M Refactoring-Core.package/RBRemoveClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBRemoveInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBRemoveMethodRefactoring.class/README.md M Refactoring-Core.package/RBRemoveParameterRefactoring.class/README.md M Refactoring-Core.package/RBRenameClassRefactoring.class/README.md M Refactoring-Core.package/RBRenameClassVariableRefactoring.class/README.md M Refactoring-Core.package/RBRenameInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBRenameMethodRefactoring.class/README.md M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/README.md M Refactoring-Core.package/RBSourceRegexRefactoring.class/README.md M Refactoring-Core.package/RBSplitCascadeRefactoring.class/README.md M Refactoring-Core.package/RBSplitCascadeRefactoring.class/instance/preconditions/findMessageNodes.st A Refactoring-Core.package/RBSplitCascadeRefactoring.class/instance/printing/storeOn_.st M Refactoring-Core.package/RBSplitClassRefactoring.class/README.md M Refactoring-Core.package/RBTemporaryToInstanceVariableRefactoring.class/README.md M Refactoring-Core.package/RBVariableRefactoring.class/README.md A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/README.md A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/definition.st A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/instance/data/methodWithCascades.st A Refactoring-Tests-Core.package/RBSplitCascadeRefactoringTest.class/instance/tests/testSplitCascadeRefactoring.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60027.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60028.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60027.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60028.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60028 18297 RBSplitCascadeRefactoring broken https://pharo.fogbugz.com/f/cases/18297 18277 Add Class comments to Refactoring-Core-Refactorings classes https://pharo.fogbugz.com/f/cases/18277 18299 Add Class comments to Refactoring-Core-Supportclasses https://pharo.fogbugz.com/f/cases/18299 18293 Add a comment to Collection>>#stdev https://pharo.fogbugz.com/f/cases/18293 18294 Remove Object >> #noteSelectionIndex:for: https://pharo.fogbugz.com/f/cases/18294 http://files.pharo.org/image/60/60028.zip

1 0

Random is not random at startup
by Peter UhnÃ¡k May 23, 2016

May 23, 2016

Hi, (cc-ing Robert Withers as he seems to be working with cryptography and security... as this seems related and may have some implications, but I am likely wrong about the implications) yesterday I've encountered a very surprising behavior I executed the same script `10 atRandom` on the same image without saving it and got the same output: while true; do pharo-vm --nodisplay latest.image --no-default-preferences eval '10 atRandom' done 10 10 10 10 10 10 Not so randomâ¦ not random at all. Apparently the default random generator uses SharedRandom pool, that is initialized only onceâ¦ so every time you start an image you get the EXACT same random seed... I think this is stupid, and I am not sure what are the security implications of this (e.g. when opening an SSL connectionâ¦ having fixed world-wide initial seed seems like an awful, awful idea), but whateverâ¦ So instead I tried to explicitly specify the Random generatorâ¦ which I can do while true; do pharo-vm --nodisplay latest.image --no-default-preferences eval '10 atRandom: Random new' done 5 5 5 5 5 Still not randomâ¦ what? while true; do pharo-vm --nodisplay latest.image --no-default-preferences eval 'Random new instVarNamed: #seed' done 426306047 426305545 426305546 426306010 So the seed is different but thanks to the magic of masking the seed, I always get the same first several bitsâ¦ thus the same result for small numbers. So if I actually want what seems like a random valueâ¦ I have to at least once run the generatorâ¦ while true; do pharo-vm --nodisplay latest.image --no-default-preferences eval '10 atRandom: (Random new next; yourself)' done 7 3 4 9 6 7 Once I start to use it the properties of the algo kick in so it's pseudo-randomâ¦ but I need to run it once to initialize it, which is wtf. My questions: 1) do we really want to have global fixed seed? 2) Random new should actually setup a usable seed so I don't need to first run it N times before I can use the value 3) Should we switch to what UUIDGenerator is usingâ¦ reading /dev/urandom for the initial seed setup? Peter

12 15

Using the stack and garbage collector?
by Alexandre Bergel May 22, 2016

May 22, 2016

Hi! The following expression give me 102: -=â=-=-=â=-=-=â=-=-=â=-= old := Smalltalk vm parameterAt: 9. 15000 factorial. new := Smalltalk vm parameterAt: 9. new - old -=â=-=-=â=-=-=â=-=-=â=-= I find that surprising. Why is the garbage collector used if factorial solely use the stack? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

weird tales about cursors and rectangle invalidations
by Esteban Lorenzano May 22, 2016

May 22, 2016

Hi, Iâve been playing a bit today with something that is puzzling me and I need some more eyes in what Iâm doing, because it might be that Iâm understanding everything wrongâ¦ but if not, then, huston, we have a bug. So, play with meâ¦ you need to create this: SystemWindow subclass: #XSystemWindow instanceVariableNames: 'iteration' classVariableNames: '' package: âXXX' XSystemWindow>>initialize super initialize. iteration := 0. XSystemWindow>>drawOn: aCanvas âDo not use transcript because it does even more crazy stuff" Stdio stdout << (iteration := iteration + 1) asString; cr; lf. super drawOn: aCanvas Then execute this in a playground: XSystemWindow new addMorph: (RubScrolledTextModel new newScrolledText) fullFrame: LayoutFrame identity; openInWorld. and then you can watch in your stdout how full window redraws with cursor blinking (it stops when window loses focus). This happens because cursor is displayed with lapsus of 700ms and is just a draw of a line with a color who is set to itâs opposite each time. Then it does "color: shownColorâ and #color: sends #changed who finalise in #invalidRect. I always thought that this invalidation mechanism works by recording âdamaged areasâ, then collecting morphs with that area and triggering the redraw of that morph. With this in mind, cursor should trigger an invalidation of itâs own area (a small portion of the screen, as you can see). I could understand that a cursor triggers the text area redraw (but that would be a âdesign flawâ, IMO)â¦ now, what I cannot understand is why blink a cursor triggers the redraw of a FULL WINDOW. When in Nautilus, that means each cursor blink triggers the redraw of one tree, four lists, some buttons and finally, the text area. IMO, this is not acceptable. What do you think? Esteban

4 6

About Smalltalk ui icons...
by stepharo May 22, 2016

May 22, 2016

loadConfigurationButton: aList <menu> aList act: [ :presenter | self onLoadFrom: presenter ] icon: Smalltalk ui icons configIcon entitled: 'Load configuration (do not install project)' why we could not have something like loadConfigurationButton: aList <menu> aList act: [ :presenter | self onLoadFrom: presenter ] icon: #configIcon entitled: 'Load configuration (do not install project)' and the class knows how to fetch it?

2 2

Turning off Spotter using internet!
by stepharo May 22, 2016

May 22, 2016

Hi guys This is hyper annoying that Spotter look for the net by default. We should turn it off. We should also improve the comment of the catalog setting because it is unclear that this is this setting that should be turned off. Stef

7 11

the fastest way to load external code
by Tudor Girba May 22, 2016

May 22, 2016

Hi, I am looking for ways to make loading of code from an st file faster. To this end, I would like to find in-image mechanisms that are not mandatory for obtaining a functional image. For example, one place I look at is SystemAnnouncer uniqueInstance, and I know that I should have no Nautilus open and that I can disable Renraku and GTExample: ReRuleManager uniqueInstance unsubscribe. GTExampleOrganizer instance stopSystemAnnouncements. What else do you see around? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Don't give to get. Just give."

4 6

New Success Story: Sysmocom: Free Software for Mobile Communication
by Marcus Denker May 22, 2016

May 22, 2016

Sysmocom: Free Software for Mobile Communication http://pharo.org/success/Sysmocom "Sysmocom is a leading provider of Free Software Mobile Communication solutions. In 2012 we have started a long term project to develop a complete ASN1, TCAP, MAP, CAP, GSN stack using the Pharo Object Environment. We have decided to use Pharo because of the increased productivity, the great tooling, the live inspection and if necessary modification of a running system to deploy a critical bugfix. Pharo has allowed us to focus on what is important. The stack was used to uncover security and privacy issues inherent to the MAP protocol design in 2014/2015. We have used the stack to build a carrier-grade AuthenticationCenter (AuC) and helped a customer to move their production traffic off a proprietary system to ours. We look forward to move a HomeLocationRegister (HLR) into production this year. said Holger Freyther CEO."

1 0