Re: Exception hacks (was Re: Changing error message)

> You should not call this GetSaleDateError but, say, SaleDateHack
hehe ;) nice pattern...  intention revealing selector is that it ? lol

> make it a Notification subclass. Unlike Error subclasses, Notification
> subclasses work fine even without an on:do: exception handler. That's
> because their #defaultAction simply answers nil instead of opening the
> debugger.
>
> If there is no handler, "SaleDateHack signal" will simply answer nil, so
> you can replace your original "Date today" code with
>
>         date := SaleDateHack signal ifNil: [Date today].
>
> (this is even better design-wise than implementing your notification's
> #defaultAction as "self resume: Date today" because you see the default
> value right where it is used, rather than hidden in the notifiction class)

cool :)

> >  (Don't tell anyone I mentioned this !^)
>
> Don't tell anyone I replied to this on the *newbies* list - I'd consider
> this well advanced. It's fun stuff anyway ;-)

maybe an advanced list ?  just kidding ;)
but this make me understand better

Thanks ;)

Cédrick
_______________________________________________
Beginners mailing list
Beginners@xxxxxxxxxxxxxxxxxxxxxxxxxx
http://lists.squeakfoundation.org/mailman/listinfo/beginners