- Pharo-dev - lists.pharo.org

[Pharo-project] [1.3 core] new pre-build Core #13159
by Marcus Denker April 17, 2011

April 17, 2011

https://gforge.inria.fr/frs/download.php/28486/PharoCore-1.3-13159.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3984 in pharo: Announcements announced when a test is runned
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Milestone-1.3 Nautilus New issue 3984 by Benjamin...(a)gmail.com: Announcements announced when a test is runned http://code.google.com/p/pharo/issues/detail?id=3984 More precisely, when the history of the test case is updated Attachments: AnnouncementsInTestCase.1.cs 2.8 KB

1 7

[Pharo-project] Issue 3967 in pharo: Announcement enhancement
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: Accepted Owner: stephane...(a)gmail.com New issue 3967 by stephane...(a)gmail.com: Announcement enhancement http://code.google.com/p/pharo/issues/detail?id=3967 Both solutions lead to remaining subscribers being notified when an error occurs. So which is decided upon, depends on which of their respective benefits are valued more. For that, it'd be nice if more than 2 people chimed in on. :) Short summary (not guaranteed to be 100% objective) Curtailing -> - Your image may crash in some cases, more specifically if you: 1) have errors in subscribers to announcements made in system-critical processes, as they will be suspended while debugging. 2) deliver announcements in a separate thread from where they're announced, and the announcing thread does so regularily. + Easy to debug. Entire call-chain available, no modification to state caused by subsequent subscribers. Restart should always lead in bug being reproduceable. The remove-from-subscriptions part of Error-handling and ifCurtailed could be combined as well, in which case #2 no longer applies. Error handling -> - Hard/impossible to debug because: 1) If your error was in ordering, debugger will step through flawlessly if restarted. 2) You start at the context of the subscriptions action, no idea where it came from. + More robust, none of the cases mentioned in Curtailing will crash your image. With the different pros/cons mentioned above in mind, here are .cs with example implementations for what both Igor / I would like. (minus remove-from-subscriptions for ifCurtailed: ) Attachments: AnnouncementErrorHandling.zip 1.7 KB

1 2

[Pharo-project] Issue 3937 in pharo: Breaking Announcement system
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: Accepted Owner: Benjamin...(a)gmail.com Labels: Milestone-1.3 New issue 3937 by Benjamin...(a)gmail.com: Breaking Announcement system http://code.google.com/p/pharo/issues/detail?id=3937 If an error occur during the propagation of an Announcement, then the further receiver will not be informed ... It can break the system easily because it breaks the synchronicity

1 3

[Pharo-project] Issue 4029 in pharo: DomainError and NaNException
by pharo＠googlecode.com April 17, 2011

April 17, 2011

Status: New Owner: ---- New issue 4029 by sven.van...(a)gmail.com: DomainError and NaNException http://code.google.com/p/pharo/issues/detail?id=4029 PharoCore 1.3 Name: Kernel-SvenVanCaekenberghe.867 Author: SvenVanCaekenberghe Time: 15 April 2011, 5:02:31 pm UUID: 476ee577-2508-4d70-bba1-91ffd1d63592 Ancestors: Kernel-SvenCamillo.866 added DomainError and NaNException added signaler instance variable to Exception with initialization in signal refactored Exception method categories

1 1

[Pharo-project] About image opening and screen shifted
by StÃ©phane Ducasse April 17, 2011

April 17, 2011

Hi I wanted to know if this was only me. But when I open an image like 13156 I get a white screen then the background always shitefd a bit and when I resize it gets right. I used 5.7.4 Stef

1 0

[Pharo-project] Pool dictionary cause problems to load package from monticello
by Guillermo Polito April 17, 2011

April 17, 2011

Hi! I have a class who has a pool dictionary defined as ... subclass: #MyClass instanceVariableNames: '' classVariableNames: '' poolDictionaries: 'MyPoolDict' .. And when I load that class from monticello, he warns me with * This package depends on the following classes: "MyPoolDict" You must resolve these dependencies before you will be able to load these definitions: * If before loading the package I declare a global named MyPoolDict it loads well... Of course, I can put a preload in a metacello configuration to declare the global, but it sucks :). Can anyone point me in the right direction? (or maybe it's a bug... :/) Thanks! Guille

4 5

Re: [Pharo-project] Issue 3188 in pharo: do we need SecurityManager?
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Updates: Labels: Milestone-1.3 Comment #1 on issue 3188 by marcus.d...(a)gmail.com: do we need SecurityManager? http://code.google.com/p/pharo/issues/detail?id=3188 let's kill it

1 3

[Pharo-project] Issue 4033 in pharo: clean up startup/shutdownlist adding, add "add before"
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4033 by marcus.d...(a)gmail.com: clean up startup/shutdownlist adding, add "add before" http://code.google.com/p/pharo/issues/detail?id=4033 - clean up startup/shutdownlist adding. - add a #addToStartUpList:before: which is what many clients actually need Attachments: ShutdownList.1.cs 7.3 KB

1 0

[Pharo-project] Issue 3573 in pharo: Failing Test: CompiledMethodTest.testPerformInSuperclassCanExecutelongMethodWithTemps
by pharo＠googlecode.com April 16, 2011

April 16, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3573 by marcus.d...(a)gmail.com: Failing Test: CompiledMethodTest.testPerformInSuperclassCanExecutelongMethodWithTemps http://code.google.com/p/pharo/issues/detail?id=3573 CompiledMethodTest.testPerformInSuperclassCanExecutelongMethodWithTemps Reason: VM Bug.

1 2