[TUSCANY-1370] C++ SDO spec compliance/portability: DataObject

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Cpp-M3
• Component/s: C++ SDO, C++ Specification
• Environment: API issues -- all platforms
• Assignee: Unassigned
• Reporter: Michael Yoder
• Created: 22/Jun/07 17:08
• Updated: 17/Jan/10 23:12
• Resolved: 29/Aug/07 14:59

Description

The specification interface DataObject.h exposes off-spec member functions, these should be made internal to the implementation.

----Original Message----
From: Michael Yoder
Sent: Thursday, June 21, 2007 6:34 PM
To: '[e-mail]'
Subject: C++ SDO spec compliance/portability: DataObject

Hi,

In the DataObject interface, these member functions are exposed which aren't in the C++ 2.1 spec:

virtual SDO_API bool hasProperty(const char* name) = 0;
virtual SDO_API bool hasProperty(const SDOString& name) = 0;

virtual SDO_API DataFactory* getDataFactory() = 0;

virtual SDO_API void setUserData(const char* path,void* value) = 0;
virtual SDO_API void setUserData(const SDOString& path, void* value) = 0;
virtual SDO_API void setUserData(unsigned int propertyIndex, void* value) = 0;
virtual SDO_API void setUserData(const Property& property, void* value) = 0;
virtual SDO_API void setUserData(void* value) = 0;
virtual SDO_API void* getUserData(const char* path) = 0;
virtual SDO_API void* getUserData(const SDOString& path) = 0;
virtual SDO_API void* getUserData(unsigned int propertyIndex) = 0;
virtual SDO_API void* getUserData(const Property& property) = 0;
virtual SDO_API void* getUserData() = 0;

virtual SDO_SPI const char* objectToXPath() = 0;

Would it be appropriate to file a Jira/patch to have these removed from the spec interface? Or alternatively a Jira to submit them to the spec committee?

Thanks,

Michael Yoder
Rogue Wave Software - [e-mail] Software Developer - HydraSDO