RE: [sv-ac] request for changes to 1460 proposal

Hi John,

Thank you for your comments. Unfortunately  I saw them too late. I fixed
all the items you pointed out, and updated the new version of the
proposal (also attaching it here). Hope it is OK now and ready for
voting.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of John Havlicek
Sent: Thursday, February 15, 2007 8:33 PM
To: sv-ac@server.eda-stds.org
Subject: [sv-ac] request for changes to 1460 proposal

Dmitry:

I have looked carefully at the updated proposal for 1460
and found a few minor items that need to be fixed.  See
the requested changes below.

Please update as soon as possible.  I still want to resolve
this item at our 2007-02-20 meeting.

Best regards,

John H.

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

1. CHANGE
   
      In Table Syntax 17-6
   
   to 
   
      In Table Syntax 17-16
   

2. CHANGE in four places

      assume property ::=

   TO

      assume_property_statement ::=

   RATIONALE:  The non-terminal is assume_property_statement.
   

3. CHANGE in two places in the 17.13 changes to Syntax 17-16
   
          {\bold_red ( assume property} property_spec {\bold_red )}
   
   TO
          {\bold_red assume property (} property_spec {\bold_red )}
   
   RATIONALE: This is the problem that Brad Pierce pointed out.  The
   open parenthesis is in the wrong place both in the old text and the
   new.  This problem was fixed for the Annex A change, but not here
   for the Section 17 change.


4. CHANGE

      assume property (abc(req,gnt,rst)); else $error("Assumption
failed.");

   TO

      assume property (abc(req,gnt,rst)) else $error("Assumption
failed.");

   RATIONALE: I don't think the current example parses with the ";"
   before "else", although I didn't check all the BNF.  We have

       action_block ::= 
          statement_or_null
          | [ statement ] else statement_or_null

   If you choose to put something in for the optional statement, you
   have to parse it as a statement, not as statement_or_null.  I
   didn't trace all the statement forms, but I am not aware of any
   that produces just ";".

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

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