On 11 July 2013 14:26, Guillaume Larcheveque <guillaume.larcheveque@gmail.com> wrote:
An exception sounds to me like something that is not expected. In my opinion, a notification is not an exception but just an information.
It's a terminology problem. The Smalltalk class Exception does not represent the same thing as the Ruby or Java Exception classes. Smalltalk's Error class is what everyone else calls an exception. A Smalltak Exception is just a thing that can communicate with some other bit of code - a handler - somewhere down the call stack. If you have any familiarity with Common Lisp, you can think of Smalltalk's Exception as a condition [1]. [1] http://www.gigamonkeys.com/book/beyond-exception-handling-conditions-and-res... frank
Esteban told me that this discussion has already occurs but I was not able to find it.
2013/7/11 Igor Stasenko <siguctua@gmail.com>
On 11 July 2013 15:06, Vincent Blondeau <vincent.blondeau@polytech-lille.net> wrote:
Hi,
For Moose on web, I have to implement the loading of a Moose Model by a HTML post request. This request send a file which have to been parsed to create a model.
The parsing launch a Job (by an UIManager) and the Job throws a JobStartNotification at his beginning. JobStartNotification is a subclass of Exception. I use a Zinc Server. So when I do the request, Zinc catch the Exception and send an error as response.
Has a Notification to be considered like an Exception and not like a catchable object, because it's just some information... ?
It is not a question that Notification should be an Exception, but question, if zinc should treat all exceptions as errors.
Cheers, Vincent
-- Best regards, Igor Stasenko.
-- Guillaume Larcheveque