[TUSCANY-1367] C++ SDO spec compliance/portability: Type::Types::IntegerType should be renamed Type::Types::IntType

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Cpp-M3
• Component/s: C++ SDO, C++ Specification
• Environment: portability issue - all platforms
• Assignee: Unassigned
• Reporter: Michael Yoder
• Created: 22/Jun/07 03:10
• Updated: 17/Jan/10 23:11
• Resolved: 23/Jun/07 08:02

Description

The C++ SDO 2.1 spec renamed Type::Types::IntegerType to Type::Types::IntType. This will need to be updated in the Type interface.

----Original Message----
From: Pete Robbins [e-mail]
Sent: Thursday, June 21, 2007 9:21 AM
To: [e-mail]
Subject: Re: SDO spec compliance/portability: Type enums

the num_type is just a convenient way to know the extent of an enum and is common practice. I guess the OpenDataObjectType must be a Tuscany specific extension to handle open types. I'd need to do some research to determine if this is missing from the spec or can be removed.

Please raise a Jira for the renaming of IntegerType.

It may be useful to raise Jiras for all these issues so we can track them.

Cheers,

On 21/06/07, Michael Yoder <[e-mail]> wrote:
>
> Hi,
>
> The Tuscany SDO C++ class Type::Types enum has these values which do
> not appear in the C++ 2.1 specification:
>
> - OpenDataObjectType
> - num_type
>
> Would it be appropriate to file a bug to remove the additional values?
> Or alternatively a bug for them to be
> submitted to the spec committee?
>
> In addition the 2.1 spec renamed the enum value "IntegerType" to
> "IntType".
>
> Would it be appropriate to file a bug to have this value renamed?
>
> Thanks,
>
> Michael Yoder
> Software Developer
> Rogue Wave Software
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>
>

–
Pete