RE: [sv-ac] my notes from Champions' meeting, Mantis 1728

Hi all,

I updated 1728 according to the champions' feedback.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of John Havlicek
Sent: Friday, November 09, 2007 10:14 PM
To: sv-ac@server.eda.org
Subject: [sv-ac] my notes from Champions' meeting

Hi Folks:

Below are my notes from yesterday's Champions' meeting regarding
SV-AC items.

This is just a heads up.  This is not the official feedback from
Champions.

J.H.

1758    SV-AC   Boolean implication -> and equivalence <->
- Friendly Amendment:  The changes to 11.4.7 should be to 11.4.8 in D4.
- SV-BC need to review this.
- SV-CC need to review this.

1728    SV-AC   Introduce "let" statement
- Comments from Shalom on missing parentheses -- see the note on Mantis.
- Example e) should have "input bit clock".  Also check mismatch of
"logic c, d"
  to "bit c, d".  Review all examples.
- SV-CC need to review this.

1668    SV-AC   Local variable initializers.
- Need to make the references to the new subclauses clearer -- use their
titles.
- Clearly identify the two documents that are part of the proposal.

1549    SV-AC   add missing formal argument types
- Need to make the references to the new subclauses clearer -- use their
titles.
- Clearly identify the two documents that are part of the proposal.
- Footnotes need to be moved into body text to be normative.  
- The check for illegal parentheses is unusual.
- Try to make a single definition for cyclic dependency.
- Consider adding $ into constant primary.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

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