Re: [sv-ac] BNF issue with concurrent_assert_item.

Subject: Re: [sv-ac] BNF issue with concurrent_assert_item.
From: Surrendra Dudani (Surrendra.Dudani@synopsys.com)
Date: Mon Apr 21 2003 - 20:46:37 PDT

• Next message: Ambar Sarkar: "[sv-ac] Some corrections/clarifications in SV3.1, draft 5"
• Previous message: Bassam Tabbara: "RE: [sv-ac] Wrong spelling of goto operator in BNF (App A.)"
• In reply to: Adam Krolnik: "[sv-ac] BNF issue with concurrent_assert_item."
• Reply: Surrendra Dudani: "Re: [sv-ac] BNF issue with concurrent_assert_item."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Good afternoon;


According to the BNF in draft 5, a concurrent_assert_item (and concurrent_cover_item)
look like this:


concurrent_assert_statement ::=
   [ block_identifier : ] assert property ( property_spec ) action_block
 | [ block_identifier : ] assert property ( property_instance ) action_block

concurrent_cover_statement ::=
   [ block_identifier : ] cover property ( property_spec ) statement_or_null
 | [ block_identifier : ] cover property ( property_instance ) statement_or_null


The problem is through procedural_assertion_item. Since it is part of a statement_item,
and a statement is defined as:

statement ::= [ block_identifier : ] statement_item


That means, this line is legal...


   iden1:  iden2:  assert property (aprop);



   Adam Krolnik
   Verification Mgr.
   LSI Logic Corp.
   Plano TX. 75074