Issue 4175: MOF Unbounded should have type long (mof-rtf)
Source: Escape Velocity (Mr. Don Baisley, donbaisley(at)live.com)
Nature: Uncategorized Issue
Severity: 
Summary: The MOF 1.3 Specification defines the constant UNBOUNDED
like this:

const unsigned long UNBOUNDED = -1;

The type should be long, not unsigned long.  The value is used
for MultiplicityType.upper which has type long.  Also, the
constant has a signed value.
Resolution: The IDL clearly contains a typo.  Fix it so that UNBOUNDED is signed
Revised Text: Change the IDL constant declaration in 3.8.1 to read: 

    const long UNBOUNDED = -1; 


Actions taken:
January 26, 2001: received issue
December 3, 2001: closed issue
Discussion: 

End of Annotations:=====
From: "Baisley, Donald E" <Donald.Baisley@unisys.com>
To: issues@omg.org
Subject: MOF Unbounded should have type long
Date: Fri, 26 Jan 2001 12:32:23 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: ~"ld9FK=!!bCPe9ZR;e9

The MOF 1.3 Specification defines the constant UNBOUNDED
like this:

const unsigned long UNBOUNDED = -1;

The type should be long, not unsigned long.  The value is used
for MultiplicityType.upper which has type long.  Also, the
constant has a signed value.

Don Baisley
Unisys


X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: mof-rtf@emerald.omg.org, crawley@dstc.edu.au
Subject: Re: issue 4175 -- MOF RTF issue 
In-Reply-To: Message from Juergen Boldt <juergen@omg.org> 
   of "Fri, 26 Jan 2001 13:50:18 EST."
   <4.2.0.58.20010126134932.0561dd30@emerald.omg.org> 
Mime-Version: 1.0
Date: Mon, 29 Jan 2001 11:00:52 +1000
From: Stephen Crawley <crawley@dstc.edu.au>
Content-Type: text/plain; charset=us-ascii
X-UIDL: bH_d94[3e95Med9gj9!!

> This is issue # 4175		Baisley, Donald E"
  <Donald.Baisley@unisys.com
> 
> MOF Unbounded should have type long
> 
> The MOF 1.3 Specification defines the constant UNBOUNDED
> like this:
> 
> const unsigned long UNBOUNDED = -1;
> 
> The type should be long, not unsigned long.  The value is used
> for MultiplicityType.upper which has type long.  Also, the
> constant has a signed value.

Agreed.

I think we can class this is an editorial errors.  The IDL and MODL in
appendices B and C (of the RTF versions of the spec) correctly say
that
"UNBOUNDED" is a "long". It is just the XMI in Appendix A and the IDL
fragment in section 3.8.1 that say it is "unsigned long".

My guess is that a typo in 3.8.1 (my mistake when editing the MOF 1.3
RTF drafts) was propagated to the XMI.  At any rate, fixing this
shouldn't cause problems.  The incorrect IDL can't be used because it
will give an IDL compilation error!  And the XMI should trigger a
Constraint in the MOF Model ... [C-52] ConstantsMustMatchType.

-- Steve



X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: mof-rtf@omg.org
Subject: Re: Issue 4175: MOF Unbounded should have type long
Mime-Version: 1.0
Date: Thu, 05 Jul 2001 21:13:10 +1000
From: Stephen Crawley <crawley@dstc.edu.au>
Resent-To: mof-rtf@omg.org
Resent-Date: Thu, 05 Jul 2001 21:27:47 +1000
Resent-From: Stephen Crawley <crawley@dstc.edu.au>
X-Scanned-By: MIMEDefang 1.0
(http://www.roaringpenguin.com/mimedefang/)
Content-Type: text/plain; charset=us-ascii
X-UIDL: 7]@!!%5Ke9S"I!!Ll`d9


> Source: Unisys (Mr. Don Baisley, Donald.Baisley@unisys.com)
> Nature: Uncategorized Issue
> Severity:
> Summary: The MOF 1.3 Specification defines the constant UNBOUNDED
> like this: 
>
>     const unsigned long UNBOUNDED = -1; 
>
> The type should be long, not unsigned long. The value is used for 
> MultiplicityType.upper which has type long. Also, the constant has a 
> signed value.

Proposed Resolution:

The IDL clearly contains a typo.  Fix it so that UNBOUNDED is signed.

Revised Text:

Change the IDL constant declaration to read:

    const long UNBOUNDED = -1;