Issue 2426:  Add interface to DTime (currency-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: The Currency submission indicates that a specific Currency instance that
 does not have an expiration date will be noted with an expiration date of
 99/99/9999. This attribute is handled via a CBO::Dtime instance, but a
 CBO::Dtime instance cannot be created or mutated to represent 99/99/9999.
 e.g. The CBO::Dtime::setMonth(mon) expects 1 <= 12, etc. Would probably be
 easiest to have two operations on CBO::Dtime to handle this. These could
 be:
         void setUnspecified() – might be handled in an implementation as
         99/99/9999.
         boolean isUnspecified() – insulates the consumer from knowing how
         the notion of “unspecified” is implemented.
 

Resolution: 
Revised Text: :Dtime instance, but a
Actions taken:
February 2, 1999: received issue
Discussion: 

End of Annotations:=====
Return-Path: <Robert_Mickley@CYBORG.COM>
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: Add interfaces to DTime to support the Currency
requirment for
unspecified dates
Issue Type: IDL Revision
Issue Description:
The Currency submission indicates that a specific Currency instance
that
does not have an expiration date will be noted with an expiration date
of
99/99/9999. This attribute is handled via a CBO::Dtime instance, but a
CBO::Dtime instance cannot be created or mutated to represent
99/99/9999.
e.g. The CBO::Dtime::setMonth(mon) expects 1 <= 12, etc. Would
probably be
easiest to have two operations on CBO::Dtime to handle this. These
could
be:
        void setUnspecified() on o f is implemented.