Issue 2418: Improve DTime exception handling (currency-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: The CBOException type currently prohibits the called software from informing the calling software as to the source of the problem that raises a CBOException. e.g. If CBO::DTime::setSeconds(63) is called, a CBOException will be raised, but the caller cannot query the CBOException caught for its exception type or description as CBOException does not currently support these constructs. In the case where many arguments are presented to a method, the caller will not know which specific argument is causing the problem. Resolution: Revised Text: :DTime::setSeconds(63) is called, a 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: Improve DTime exception handling Issue Type: IDL Revision Issue Description: The CBOException type currently prohibits the called software from informing the calling software as to the source of the problem that raises a CBOException. e.g. If CBO::DTime::setSeconds(63) is called, a CBOException will be raised, but the caller cannot query the CBOException caught for its exception type or description as CBOException does not currently support these constructs. In the case where many arguments are presented to a method, the caller will not know which specific argument is causing the problem.