Issue 18299: Semantics of overriding an attribute not clearly specified (dds-xtypes-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Clarification
Severity: Minor
Summary: Is it allowed to have a parent and a child struct share an attribute with the same name?
* In most OO-languages this is allowed.
* However, in scenario's like type-refactoring this will cause huge problems.


We should clearly specify whether or not this is allowed, and when allowed we should clearly describe the consequences.
Resolution: 
Revised Text: 
Actions taken:
December 12, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 12 Dec 2012 07:44:02 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-Tracker: AAAAAA==


*******************************************************************************
Name:            Erik Hendriks
Employer:        PrismTech
mailFrom:        erik.hendriks@prismtech,com
Terms_Agreement: I agree
Specification:   Extensible and Dynamic Topic Types for DDS
Section:         7.3.1.10.1
FormalNumber:    ptc/2012-03-26
Version:         1.0
Doc_Year:        2012
Doc_Month:       February
Doc_Day:         Day
Page:            76
Title:           Semantics of overriding an attribute not clearly specified
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


Is it allowed to have a parent and a child struct share an attribute with the same name?
* In most OO-languages this is allowed.
* However, in scenario's like type-refactoring this will cause huge problems.


We should clearly specify whether or not this is allowed, and when allowed we should clearly describe the consequences.