[TUSCANY-1368] C++ SDO portability: class interface Type off-spec enum values

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Cpp-M3
• Component/s: C++ SDO, C++ Specification
• Assignee: Unassigned
• Reporter: Michael Yoder
• Created: 22/Jun/07 03:15
• Updated: 17/Jan/10 23:12
• Resolved: 29/Aug/07 15:00

Description

C++ SDO specification class interface Type has enum values ("OpenDataObjectType", "num_type")which are not in the specification, and are being used externally by SCA. It would seem that for SDO portability these should be taken internal to SDO or submitted to the spec committee.

----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