- Pharo-dev - lists.pharo.org

PhExample repository
by Norbert Hartl July 10, 2013

July 10, 2013

Which one is the right repository? http://smalltalkhub.com/#!/~PharoExtras/Phexample or http://smalltalkhub.com/#!/~Phexample/Phexample And if they are copies of each other could you please change one of those to include a comment/pointer that the other one is in use? Norbert

3 4

Nice VM crash
by Jan Vrany July 10, 2013

July 10, 2013

Hi guys, getting bored? Looking for an excuse to play with GDB? Here we go: https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchm… Okay, seriously: build 17 from Jun 17 did not crash - the Smalltalk code was the same. Jenkins executes following script: === export PATH=/usr/bin:$PATH IMAGE_BASE=CalipeL-S-$BUILD_NUMBER IMAGE=$IMAGE_BASE.image if [ ! -r Pharo.image ]; then wget -O- get.pharo.org | bash fi ./pharo Pharo.image save $IMAGE_BASE ./pharo $IMAGE config http://smalltalkhub.com/mc/JanVrany/CalipeL-S/main ConfigurationOfCalipeLS --install=0.1 ./pharo $IMAGE benchmark --json -o results.json BenchmarkMicro === System is running stock 32bit debian stable on VMWare ESX 5.1. I can provide more details if you like (and ask what exactly :-) Best, Jan

4 4

[regression reporter]regression occurred
by no-reply＠ci.inria.fr July 10, 2013

July 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 1 regressions found. Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr July 10, 2013

July 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 1 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge

1 0

[update 3.0] #30263
by Marcus Denker July 10, 2013

July 10, 2013

30263 ----- 11142 For 3.0: 11102 FileSystemError https://pharo.fogbugz.com/f/cases/1114 10466 Better interruption https://pharo.fogbugz.com/f/cases/10466 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.42.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1514.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Disk-MarcusDenker.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FileSystem-Core-MarcusDenker.…

1 1

[regression reporter]regression occurred
by no-reply＠ci.inria.fr July 10, 2013

July 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 2 regressions found. Tests.Polymorph.Widgets.FileDialogWindowTest.testIssue6406 Tests.Release.ReleaseTest.testObsoleteClasses

1 0

[update 2.0] #20612
by Marcus Denker July 10, 2013

July 10, 2013

20612 ----- 10569 Backport 2.0: Better Interrruptionche https://pharo.fogbugz.com/f/cases/10569 10940 Backport 2.0: 10925 Use caching in Gofer https://pharo.fogbugz.com/f/cases/10940 Diff information: http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.782.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1350.diff http://ss3.gemstone.com/ss/Pharo20/Gofer-Core-MarcusDenker.194.diff

2 1

July 10, 2013

Hello pharoers, Recently I have been looking at the Pharo thisContext capabilities, in order to perhaps one day in the far future edit its implementation with the Pharo dev team. Nothing is planned or confirmed, it is just to discuss. A context has instances variables (method closureOrNil receiver stackp sender pc) and holds the arguments and temporaries. Now I'd like to know what context's state do we modify, and what states are just internal representations ? For example, it seems that you can do 'thisContext receiver: #foo', but you cannot with Cog. SomeClass>>foo thisContext receiver: #foo. ^ self In workspace, evaluating: 1 to: 5 do: [:i | Transcript show: SomeClass new foo ] Transcript result (with Cog): foo foo a SomeClass a SomeClass a SomeClass Transcript result (with Stack or Vanilla): foo foo foo foo foo Now as no one has ever complained, I guess this feature is not used. As far as I know, the real use cases of the context seems to be: - setting and gettings temporaries - setting and getting the sender of a context - setting and getting the pc - getting method, closureOrNil, receiver, stackp, arguments but NOT setting them Now setting the sender of a context seems to be used only in two cases: - continuations (as seaside continuations) - exception implementation So imagine that in the future you would have a context that can be accessed in read-only, where you could only: - set the temporaries (but not arguments) - set the pc (or something equivalent, as set the currently executed ast node) - use continuations (exceptions can be implemented on top of continuations) I would like to know if there are things that you do now and that you would not be able to do with a context like that. For non meta developer (like enterprise app developer) I guess it will not change anything, but I want to know if you implemented a framework as seaside, does it requires other things from the context and why ? Thanks for answering,

4 8

should:raise:description:
by Camillo Bruni July 10, 2013

July 10, 2013

I continue my rant with should:raise:description: a) self should: [ Error signal: 'error message' ] raise: Halt description: 'message'. b) self should: [ 1 + 2 ] raise: Halt description: 'message'. In the first case you do not get the 'message' but 'error message'. In the second case you get the 'message'. Does the description make sense in this case? 1. if you signal Halt everything is fine 2. Every other case is a failure 3. In case a) an internal failure happens so the test fails anyway, fine, but no description 4. A strange? case where the tests actually DO pass but we nevertheless want to print a description. Can anybody give me a convincing case for 4? Sorry, after this I will stop :D

4 5

[regression reporter]regression occurred
by no-reply＠ci.inria.fr July 10, 2013

July 10, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 1 regressions found. Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory

1 0