Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-15 Thread pharo
Comment #13 on issue 3817 by marianopeck: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Thanks Guille. -1 too And +1 to use special errors when necessary (again, check my projects and you will see I do this)

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-15 Thread pharo
Comment #14 on issue 3817 by toon.ver...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 I totally agree with Camillo. Error: does not convey any meaning. Even though your code currently does not handle the error specifically, you might

[Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Status: New Owner: New issue 3817 by camillob...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Object error: should be deprecated. It encourages the usage of raw Errors too much. Using specialized errors everywhere in the system should be

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #1 on issue 3817 by marianopeck: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 I think this change is too radical, and it should be discussed. I think a lot of packages will be broken. Is this part of ANSI ?

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #2 on issue 3817 by camillob...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 it is not too radical for 1.3. Using Error is as useful as saying that something went wrong somewhere. You don't want that. I agree that `self error:

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #3 on issue 3817 by guillerm...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 I don't fully agree. You have to use particular exception types, when you want to give them a special treatment (by code). Most of the times, the error

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #4 on issue 3817 by ryd...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Yes, Object#error: is part of the ANSI protocol. I agree in spirit 100% with what Camillo is saying though. To me, a better approach would be to lead by example.

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #5 on issue 3817 by stephane...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 only :) and I'm sure that I fixed some of them already :). What would be good is to perform an analysis to see their usage.

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #6 on issue 3817 by marianopeck: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Your point of view, is .. only one point of view. If you check my code, you will see that sometimes, I reify an exception in a subclass of Error. This is because of the

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #7 on issue 3817 by camillob...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 I agree that `self error:` is amazingly useful, but it should be used with caution. Lazyness is never an argument for keeping a partly broken design! It

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #8 on issue 3817 by guillerm...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 What's a broken design? Tell me how does a more specific subclass of Error help you if you don't give it an special treatment. If you don't do that,

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #9 on issue 3817 by camillob...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Just to give an example of what I mean. In Java the general error handling is mainly based on a set of specific classes, the generic Exception is almost

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #10 on issue 3817 by camillob...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 http://www.springerlink.com/content/e7170h6104136721/ seems to be a thorough study on exception handling. One important claim is, that in order to

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #11 on issue 3817 by cesar.ra...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Camillo, Regarding your comment in #6, I think replacing `Object error:` with something like... is not an option, except if you're canvassing for

Re: [Pharo-project] Issue 3817 in pharo: make Object error: deprecated

2011-03-14 Thread pharo
Comment #12 on issue 3817 by guillerm...@gmail.com: make Object error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Lets convey that if you have an InvalidArgumentException, that's a bug in your code. There's no way that it can be handled. It is no useful. You can