[sv-cc] review of 0226 implementation in draft8

Hi,

 

Gosh this was fun!  Clause 36, 38, and Annex C and L were implemented
correctly.  Clause 37 has some minor cross reference issues that were
not what was documented and one issue with diagram 37.39 Frames.  Annex
N has been discussed and concur with the concerns raised about numbering
issues with vpiAllocScheme and cbEndOfObject.  These are editorial
issues which should be corrected. There is also an omission of vpiObjId,
as Abi noted a couple of weeks ago.  It was the first implementation of
0226 changes but not in any subsequent revisions of our Annex N inputs
to the editor. Clearly, I dropped it and we all missed it across at
least 2 reviews.  It has always been on the information model diagram,
of course.  I don't care how we handle it procedurally, but it would be
just sad to drop the ball on it again if we should defer it. 

 

Regards, John

---------------------

The details are:

 

Page 879, 37.3.7 is currently:

 

Other transient objects include:

1) threads (see 37.39).

2) outdated and out of scope references made within a thread

3) iterators (objects of type vpiIterator), which are created by calls
to vpi_iterate() (see 37.23).

4) a vpiSchedEvent created by vpi_put_value() (see 37.34)

5) callbacks (see 37.36).

 

and should be:

 

Other transient objects include:

1) threads (see 37.40).

2) outdated and out of scope references made within a thread

3) iterators (objects of type vpiIterator), which are created by calls
to vpi_iterate() (see 38.23).

4) a vpiSchedEvent created by vpi_put_value() (see 38.34)

5) callbacks (see 38.36).

 

On page 915, in note 10) of diagram  37.29 Class variables and class
objects, it should be:

 

10) For details on class object specific callbacks, see 38.36.1

 

In diagram 37.39 Frames, there remains a property:

-> validity

int: vpiValid

 

which no longer exists in the information model.  I had removed this
from the framemaker version showing "changes only" for this clause.  In
the full version of clause 37, this property was still there.  As you
all know, it easier for everyone to review a succinct changes only
version and much easier for the editor to incorporate my integrated
version of those changes. This was my editorial mistake and cleverly
hidden, I might add.

 

I will not repeat the Annex N changes to editor assigned values, as
Charlie documented them adequately in his Mantis note to 0226.  I will
emphasize that we must have property vpiObjId in Annex N with an
appropriately assigned value:

 

#define vpiObjId                 <editor value> /* Mantis 2226 */

 

 

 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.