Issue 2365: Description of Exception handling semantics (currency-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: Text needs to be added to describe what causes an exception to be raised for a given interface, when the semantics/preconditions for the interface have been violated (vs. exceptions specific to a vendor ’s implementation). e.g. Money.[gs]etValue(), MoneyFormatter.[gs]etFormattingString(), etc. It appears that most every interface raises (FbcException), but quite often the text which describes which exceptions can be raised, in terms of ExceptionType and under what conditions the exception is raised/thrown, has not been detailed. A detailed pass through the entire FbcCurrency spec should be conducted with attention paid to each interface and its exception generating details. Resolution: Revised Text: Actions taken: January 11, 1999: received issue Discussion: End of Annotations:===== Return-Path: From: Robert_Mickley@CYBORG.COM X-Lotus-FromDomain: CYBORG@CYBORG_NET To: issues@omg.org cc: Robert_Mickley@CYBORG.COM, Amy_Griffis@CYBORG.COM Date: Mon, 11 Jan 1999 21:28:52 -0700 Subject: Currency RTF Issues Content-Disposition: inline Today is the deadline for comments for the Currency RTF. Below is an itemized list of additions to that list. Issue Title: Description of Exception handling semantics Issue Type: Text Revision Issue Description: Text needs to be added to describe what causes an exception to be raised for a given interface, when the semantics/preconditions for the interface have been violated (vs. exceptione.g. Money.[gs]etValue(), MoneyFormatter.[gs]etFormattingString(), etc. It appears that most every interface raises (FbcException), but quite often the text which describes which exceptions can be raised, in terms of ExceptionType and under what conditions the exception is raised/thrown, has not been detailed. A detailed pass through the entire FbcCurrency spec should be conducted with attention paid to each interface and its exception generating details.