On Wed, Jul 6, 2011 at 12:51 PM, Jules Kerssemakers <jules.kerssemak...@googlemail.com> wrote: > One of java's core strengths in general is that the class-hierarchies allow > you a lot of rigid control over program flow and what can and cannot be > done. It would be a waste to throw that away by using only one CDK-exception > or only Java-Core exceptions.
Interesting you bring this up. Exceptions should not be used for code flow. I guess this must be part of this design: for every CDKException (or subclass) we throw, we must have an API that allows checking if the required condition is fulfilled. Egon -- Dr E.L. Willighagen Postdoctoral Researcher Institutet för miljömedicin Karolinska Institutet (http://ki.se/imm) Homepage: http://egonw.github.com/ LinkedIn: http://se.linkedin.com/in/egonw Blog: http://chem-bla-ics.blogspot.com/ PubList: http://www.citeulike.org/user/egonw/tag/papers ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Cdk-user mailing list Cdk-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdk-user
