Or remove the absurd coupling between subclassing and grouping exceptions/events (or whatever name you prefer to use :-) ) that leads to absurd/depth/big exception/events hierarchies :-)
On Thu, Oct 6, 2011 at 12:49 PM, Lukas Renggli <[email protected]> wrote: > On 6 October 2011 17:40, Igor Stasenko <[email protected]> wrote: > > On 6 October 2011 17:24, Lukas Renggli <[email protected]> wrote: > >>>> why wasting an energy on something, which not gives any benefits? > >>> > >>> There is a benefit when you teach Pharo and write a book. > >> > >> Then you should make the Exception hierarchy a subclass of Event too > >> and rename all exceptions, because they are all (exceptional) events > >> too. > >> > >>>> i completely agree that proper naming is important. but the framework > >>>> was originally designed not by us, > >>>> and i think its not quite correct to rename it without asking the > author. > >>> > >>> This is what this email is about :-) > >> > >> Puns aside: Why not just remove the Announcement class altogether? It > >> used to be empty in the original implementation and serves no real > >> purpose other than grouping its subclasses. Any object can potentially > >> represent an event. > >> > > err.. an Announcement playing own role as a root class for all > announcements. > > In same way as Exception is a root of all exceptions, so if you want > > to handle all exceptions you putting Exception class. > > If you remove the notion of root, then you will need to introduce > > something else in order to satisfy 'i wanna handle all > > exceptions/events , > > no matter what they are'. > > Object would be your choice for all events then. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- *Hernán Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: [email protected] site: http://www.10Pines.com <http://www.10pines.com/>* Address: Paraguay 523, Floor 7 N, Buenos Aires, Argentina
