[sv-ec] RE: Mantis 1356 rev 16

From: Tipp, Brandon P <brandon.p.tipp@intel.com>
Date: Mon Nov 21 2011 - 10:48:56 PST

Rev16 attached with the latest editorial fixes. Sorry for all the re-sends, but I wanted to give everyone as much time as possible with the latest revs.
See below...

From: Bresticker, Shalom
Sent: Monday, November 21, 2011 11:42 AM
To: Tipp, Brandon P; sv-ec@eda.org
Subject: RE: Mantis 1356 rev 16

OK, this looks reasonable.

Just need some editorial tweaks:

In 8.26.6.3:

Since these parameters originate from the same interface class, IntfBase, only one copy of SIZE shall be inherited into IntfExt3 so it shall not be considered a conflict.

The second IntfExt3 should be in code font.
[Tipp, Brandon P] Fixed

In the next paragraph:

Each interface class specialization is considered as though is a unique interface class type.

Either "as though it is" or simply "considered a unique interface class type".
[Tipp, Brandon P] Changed to "as though it is". I don't want to make it as strong as "considered a unique interface class type" since that stronger language could have unintended consequences.

Last sentence in the subclause:

Each of these parameterizations of IntfBase is a specialization, therefore there is no diamond problem and there are conflicts of the parameter T and method funcBase that must be resolved.

Should be "diamond relationship".
[Tipp, Brandon P] Thanks for catching that. Fixed.

Thanks,
Shalom

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Tipp, Brandon P
Sent: Monday, November 21, 2011 7:37 PM
To: Tipp, Brandon P; sv-ec@eda.org
Cc: Tipp, Brandon P
Subject: [sv-ec] RE: Mantis 1356 rev 16

Re-sending rev 16 with a few more minor changes.

* One more editorial change (which -> that)

* Re-re-worded "Diamond problem", previously "Diamond inheritance," to the new and improved "Diamond relationship"
-Brandon

From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Tipp, Brandon P
Sent: Friday, November 18, 2011 11:45 AM
To: sv-ec@eda.org
Subject: [sv-ec] Mantis 1356 rev 16

All,

Please review 1356 rev16 for Monday's meeting. The docx showing rev15->rev16 changes is attached. The following (significant) changes were made since rev14 was approved by the SV-EC...

Rev14->rev15

* Various formatting and typo changes

* Deleted this line "This interface implementation allows classes to support common behaviors without sharing implementations." from the first paragraph (feedback was that it is both confusing and redundant)
Rev15->rev16

* Re-numbered references due to mantis 3001 which inserted 8.8

* Various formatting updates

* Re-worded a lot of the text under Name conflicts and resolution and the sub-sections

* Major changes to the wording in the "Diamond inheritance" section. Re-named it "Diamond problem" since I received feedback to try to remove the last references to "inheritance" w.r.t. interface class implementations.

* Added a paragraph to the end of 8.56.9 to clarify that pre_randomize() and post_randomize() work with interface class handles.

The following feedback items are still open with Shalom:

* Shalom had feedback that it is not clear "whether an implemented non-inherited method needs to be declared virtual. Assuming that to be true, it is probably good to say so explicitly." I replied that is already explicitly stated by the first paragraph on page 3. I haven't received a reply to that yet.

* Shalom is still reviewing the updated text in the "Diamond problem" section.

-Brandon

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Received on Mon Nov 21 10:49:32 2011

This archive was generated by hypermail 2.1.8 : Mon Nov 21 2011 - 10:49:35 PST