Forums

Am 29.07.2011 12:26, schrieb Nicolas Rodriguez:
> Hello,
>
> I would like to replace any use of the java Error class by our own
> exception, extending RuntimeException.

I agree!

> Like this the signature of the methods will not change but with an error
> you are not getting any information, the message is not displayed
> when the stack trace is shown. It just tell that there as been and
> Exception (without message and without saying that it was a
> PropertyError or a LevelAndVersionError)

Sounds reasonable.

> The only thing we would have to do, I think is to make XMLerror extends
> RuntimeException instead or Error.

Could you please briefly summarize the difference between both
(RuntimeException and Error)?

> What do you think ??
>
> We could also make some of the jsbml specific errors extends directly
> SBMLException ?

Also reasonable.

> But I don't think we need to change the name of our specific errors
>

Yes, but maybe inheritance relationships. Should we include errors also
into our type hierarchy diagram?

Cheers
Andreas

--
Dr. Andreas Dräger
University of Tuebingen
Center for Bioinformatics Tuebingen (ZBIT)
Sand 1
72076 Tübingen
Germany

Phone: +49-7071-29-78982
Fax: +49-7071-29-5091
____________________________________________________________
To manage your jsbml-development list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/jsbml-development

For a web interface to the jsbml-development mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the jsbml-development list,
contact sbml-team@caltech.edu