"Raoul De Kezel" <✉hotmail.com> wrote in message news:✉forums.inprise.com...
> ... like any good design, this specification is in turn > driven by the needs and usage pattern of its clients. > Most arbitrary exception specifications will be useless
strategy and therefore need "reworking". Seldom are you in a position where all the code is written by the same team, using the same strategies and styles for the same single purpose. So learning to integrate code from other people has to be part of your "bag'o'tricks".
> When more than one usage pattern is common, > more than one exception specification > will be needed.
in all but the simplest cases. Kristofer