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

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

by Camillo Bruni

On 2011-04-14, at 14:19, Hernan Wilkinson wrote: > > > On Thu, Apr 14, 2011 at 9:08 AM, Toon Verwaest <toon.verwaest(a)gmail.com> wrote: > Right, so you confirm the experience of Dale. > > In the case of flagging errors without classes, do you generally just use a simple symbol, or concatenate strings to convey more details? This last seems somehow a bad idea... but maybe if it's never caught it's not so relevant? > > I don't understand exactly what you mean... if you are suggesting using error codes over exceptions, no, that is not may point. Exceptions are the right tool to get rid of the repeated/error prone code you create when using error codes, there is not doubt about it. > What I'm saying is that from the handling point of view you only need to identify the exception to handle, and matching the class of the exception with identifying the exception is not the only way (I showed another way in a previous mail). > Also, categorizing exception types using subclassing does not seem to be a good idea either... it is common use now, but that does not mean it is good. Sometimes you want to categorize exceptions in a different way that your exception class hierarchy forces you, and when that happens it is really a pain. But right now that is possible by concatenating Exceptions, generating ExceptionSets, which you could even generate upfront, so complexity-wise it is the same as using symbols as identifiers in a generic Exception class. But I agree finding the right balance of how many exception classes to use is not easy. However, we are still far from that in Pharo..., even worse, since no one uses explicit error classes no one uses them. And certainly there should be another way to catch errors than just by relying on the type / class. Sometimes it would be nice to be able to catch errors depending on the place they were thrown, for instance only handle exceptions thrown in my own methods / my package... And concerning the IDE, we need a lot of improvements there, the current design and functionality in Pharo at least, resembles more a system from the 70'ies than a more recent ide.

April 14, 2011

Re: [Pharo-project] Issue 3148 in pharo: Proposal: adding 261 named colors

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 4018 Comment #3 on issue 3148 by marcus.d...(a)gmail.com: Proposal: adding 261 named colors http://code.google.com/p/pharo/issues/detail?id=3148 (No comment was entered for this change.)

April 14, 2011

Re: [Pharo-project] Issue 4018 in pharo: Color class enhancement

by pharo＠googlecode.com

Comment #3 on issue 4018 by marcus.d...(a)gmail.com: Color class enhancement http://code.google.com/p/pharo/issues/detail?id=4018 Issue 3148 has been merged into this issue.

April 14, 2011

Re: [Pharo-project] Issue 4018 in pharo: Color class enhancement

by Marcus Denker

And pleast, please have a look at old tracker entries... http://code.google.com/p/pharo/issues/detail?id=3148 On Apr 14, 2011, at 3:11 PM, pharo(a)googlecode.com wrote: > > Comment #2 on issue 4018 by alexandr...(a)gmail.com: Color class enhancement > http://code.google.com/p/pharo/issues/detail?id=4018 > > XKCDColors, written by Johan Fabry > > Attachments: > XKCDColor.st 12.1 KB > XKCDColorTest.st 458 bytes > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 14, 2011

Re: [Pharo-project] Issue 4018 in pharo: Color class enhancement

by pharo＠googlecode.com

Comment #2 on issue 4018 by alexandr...(a)gmail.com: Color class enhancement http://code.google.com/p/pharo/issues/detail?id=4018 XKCDColors, written by Johan Fabry Attachments: XKCDColor.st 12.1 KB XKCDColorTest.st 458 bytes

April 14, 2011

Re: [Pharo-project] Issue 4018 in pharo: Color class enhancement

by pharo＠googlecode.com

Comment #1 on issue 4018 by Torsten....(a)astares.de: Color class enhancement http://code.google.com/p/pharo/issues/detail?id=4018 take care, "*mondrian-core-accessing" is used for method category

April 14, 2011

Re: [Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #4 on issue 3986 by marcus.d...(a)gmail.com: Bug with Delay during clock rollover http://code.google.com/p/pharo/issues/detail?id=3986 (No comment was entered for this change.)

April 14, 2011

Re: [Pharo-project] Issue 4020 in pharo: Improve cleanUpForRelease and cleanUpForProduction

by pharo＠googlecode.com

Comment #1 on issue 4020 by marcus.d...(a)gmail.com: Improve cleanUpForRelease and cleanUpForProduction http://code.google.com/p/pharo/issues/detail?id=4020 Issue 4021 has been merged into this issue.

April 14, 2011

Re: [Pharo-project] Issue 4021 in pharo: Improve cleanUpForRelease and cleanUpForProduction

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 4020 Comment #1 on issue 4021 by marcus.d...(a)gmail.com: Improve cleanUpForRelease and cleanUpForProduction http://code.google.com/p/pharo/issues/detail?id=4021 (No comment was entered for this change.)

April 14, 2011

[Pharo-project] Issue 4021 in pharo: Improve cleanUpForRelease and cleanUpForProduction

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4021 by marcus.d...(a)gmail.com: Improve cleanUpForRelease and cleanUpForProduction http://code.google.com/p/pharo/issues/detail?id=4021 cleanUpForRelease: - call BitBlt cleanUp Production: - unload Helystem fixed - unload Deprecated12 and Deprecated13 - unload SimpleMorphic Attachments: betterCleanUpMethods.1.cs 4.5 KB

April 14, 2011