RE: [sv-ac] question on clocking blocks

From: Bassam Tabbara <Bassam.Tabbara_at_.....>
Date: Fri Jun 09 2006 - 10:11:04 PDT
Hi Lisa,
 
It's because the clocking block is used for *declaration* only.
 
Thx.
-Bassam.
 

________________________________

From: owner-sv-ac@verilog.org [mailto:owner-sv-ac@verilog.org] On Behalf
Of Lisa Piper
Sent: Friday, June 09, 2006 7:18 AM
To: sv-ac@verilog.org
Subject: [sv-ac] question on clocking blocks



Why is it that concurrent_assertion_statements are not allowed in
clocking blocks?  If you can define properties and sequences in a
clocking block, then why can't you assert them too?  I think it is
better to be able to keep related components together.   I should not
need to do hierarchical referencing to assert my property or use my
sequence.

 

Lisa

 

 

 

 

clocking_declaration ::=

[ default ] clocking [ clocking_identifier ] clocking_event ;

{ clocking_item }

endclocking [ : clocking_identifier ]

 

clocking_item ::=

default default_skew ;

| clocking_direction list_of_clocking_decl_assign ;

| { attribute_instance } concurrent_assertion_item_declaration

 

concurrent_assertion_item_declaration ::=

                property_declaration

                | sequence_declaration

 
Received on Fri Jun 9 10:10:37 2006

This archive was generated by hypermail 2.1.8 : Fri Jun 09 2006 - 10:10:53 PDT