OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sdo message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE 120: Define the "undefined state" after projection


Title: [NEW ISSUE]: Define the "undefined state" after projection
http://www.osoa.org/jira/browse/SDO-120


Von: Barack, Ron [mailto:ron.barack@sap.com]
Gesendet: Mittwoch, 9. April 2008 11:37
An: sdo@lists.oasis-open.org
Betreff: [sdo] [NEW ISSUE]: Define the "undefined state" after projection

RAISER:  Ron Barack

CATEGORY:
Topic 7:  Type System and Helpers
Topic 10: Containment

DESCRIPTION:
The resolution of Issue 66 says that the project method leaves the data object given as an argument in an "undefined state".  This was intended to allow implementation to choose either of two approaches:

A)  both the object and its projection could be kept "live".  That is, both the original object and ist projection are usable after the call.

B) the object has become unusable in the original context, perhaps because the internal data structures used by the object are now set up for the new contexts.  Indeed, it is possible that the object returned by the project is the same object as was given as an argument.

We should consider specifying which of these two alternatives is "correct".




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]