From: Francoise Martinolle (firstname.lastname@example.org)
Date: Mon Jun 28 2004 - 07:20:00 PDT
The following reply was made to PR errata/530; it has been noted by GNATS.
From: Francoise Martinolle <email@example.com>
To: firstname.lastname@example.org, email@example.com
Subject: errata/530: comments
Date: Mon, 28 Jun 2004 10:12:31 -0400 (EDT)
The changes are good but I think that we also agreed on having
2 tchk term classes, one which would be
accessible from the vpiTchkRefTerm method and anther one which would be
accessible from the vpiTchkDataTerm method. Basically now the diagram has
one arrow with 2 labels which is not correct.
Only onr occurence oft he tchk term class should be bold (definition) while
the other would be a reference.
>X-Authentication-Warning: isvw3.cadence.com: iscan owned process doing -bs
>Date: Fri, 25 Jun 2004 06:51:10 -0700
>Subject: errata/530: PROPOSAL - 26.6.17: expr class does not contain
vpiTchkTerm - should model different
>X-pstn-levels: (S:75.06122/99.90000 R:95.9108 P:95.9108 M:99.8514 C:79.5348 )
>X-Received: By mailgate.Cadence.COM as GAA25738 at Fri Jun 25 06:53:00 2004
>This is just to update the proposal according to Charles
>Dawson's modification from Feb. 2. Further modified by Jim Vellenga on June
>Replace the expr dotted enclosure which is accessed via the
>one to many transition from tchk with an unnamed class
>containing expr and tchk term. Label the one to many
>CHANGE Note 1 to:
>For the timing checks in Section 15.1, the relationship
>vpiTchkRefTerm shall denote the reference_event or
>controlled_reference_event, while vpiTchkDataTerm shall
>denote the data_event, if any.
>CHANGE Note 2 to:
>When iterating over vpiExp from a tchk, the handles
>returned for a reference_event, a
>controlled_reference_event, or a data_event shall have
>the type vpiTchkTerm. All other arguments shall have
>types matching the expression.
This archive was generated by hypermail 2.1.4
: Mon Jun 28 2004 - 07:20:06 PDT
sponsored by Boyd Technology, Inc.