April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Updates: Status: Started Comment #6 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 Nope. Now we don't get a debug log anymore but it nevertheless hangs. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/219/console

April 13, 2011

[Pharo-project] Issue 4005 in pharo: Disconnect SecurityManager

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4005 by marcus.d...(a)gmail.com: Disconnect SecurityManager http://code.google.com/p/pharo/issues/detail?id=4005 ... remove all but one references to security Manager. Later: - remove from startup lost - fix others that depend on being added after/before to the list - remove class (there is another issue for that) Attachments: SecurityManagerClean.1.cs 14.3 KB

April 13, 2011

Re: [Pharo-project] Meanwhile, at another vm

by StÃ©phane Ducasse

still this can always be interesting to learn your limit and dependencies. Stef On Apr 13, 2011, at 9:32 AM, Philippe Marschall wrote: > On 04/13/2011 09:00 AM, StÃ©phane Ducasse wrote: >> I really interested to see if pharo would run on a JVM. > > Probably not. I mean you all the code relying on primitives, all the > code relying on ByteString having the same memory layout as ByteArray, > all the code relying on the scheduler being non-preemptive, all the > code relying on #become: and so forth. > > Cheers > Philippe > >

April 13, 2011

Re: [Pharo-project] Improving Pharo's Exception Hierarchy

by Camillo Bruni

Hey, What I've seen so far and I like is to use small helper methods to signal exceptions: "usage" Dictionary >> at: aKey ... self keyNotFound: aKey. "helper method to fill the exceptions params" Dictionary >> keyNotFound: aKey KeyNotFoundException signalWithKey: aKey "helper to signal an Exception" KeyNotFoundException class >> signalWithKey: aKey self new key: aKey; signal. At least one of the helper methods should be present to make the code more readable, I think. And as Mariano pointed out, there should be a convention on the naming: I am still not sure about suffixing the exception classes with "Exception", but I guess this is a good thing to do. Though I must say that I omitted it so far ;) and just put the verb there, but that can be easily changed. The exception hierarchy looks nice ;), I think in this matter we can learn a bit from Java. And I would certainly like to see these error messages infect the whole system ;). camillo On 2011-04-13, at 11:03, Sven Van Caekenberghe wrote: > On 13 Apr 2011, at 10:50, Mariano Martinez Peck wrote: >> You probably know the PharoByExample chapter on exceptions, >> but just in case: https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.p… > > Seems like the right kind of preparation, I will reread it. > I love written documentation. > Thanks! > > Sven

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Updates: Status: FixToInclude Comment #5 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 I think the problem is a exception handler that swallows all Exceptions (ProgressNotification, too) in headless mode. (leftover from before the real headless mode). fix attached. Attachments: SmalltalkImage-sendtoClassesNamedInwith.st 886 bytes

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #4 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 Now the script loads but we get a walkback. One that does not kill the image interestingly. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/ws/PharoCore-…

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #3 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 I think I found it. I added CommandLine initialize to the postscript but forgot CodeLoader initialize

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #2 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 So I did a new prebuild. https://gforge.inria.fr/frs/download.php/28478/PharoCore-1.3-13147.zip But now Hudson hangs when loading the script. So something is completely broken. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/215/console

April 13, 2011

Re: [Pharo-project] Issue 4002 in pharo: AbstractLauncher needs to be removed

by pharo＠googlecode.com

Comment #1 on issue 4002 by ryd...(a)gmail.com: AbstractLauncher needs to be removed http://code.google.com/p/pharo/issues/detail?id=4002 Security? That script could contain sinister arbitrary code! :)

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #1 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 I think changing how scripts are loaded in an image started with a script is not good. The image itself when updated seems good. So I update the pre-build and we will see.

April 13, 2011