RE: [sv-bc] Usage of named event

From: Rich, Dave <Dave_Rich_at_.....>
Date: Tue Mar 25 2008 - 13:12:01 PDT
Mantis 2219 tries to clarify that a variable of the event data type
contains a handle to a "synchronization object". There really is no
longer any such thing as a "named event", but it was too late in the PAR
to change that much text.

The only allowed operations on event data type variables are triggering,
event controls and, similar to other handle types, comparison with like
types and assignment.

The LRM does not currently allow any handle data types as part of a
logical expression, so both examples are technically illegal. However,
some implementations do support this. (non-null is true, null is false)

Dave


> -----Original Message-----
> From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org]
On
> Behalf Of Surya Pratik Saha
> Sent: Tuesday, March 25, 2008 12:10 AM
> To: sv-ec@server.eda.org; sv-bc@server.eda.org
> Subject: [sv-bc] Usage of named event
> 
> Hi,
> Verilog 1364-2005 LRM introduces the named event declaration. Section
> 9.7.3 mentions where an event can be allowed. But it is not mentioned
> usage of other places is illegal. Consider the following e.g.:
> 
> module top;
> event line_end_event;
> initial
> begin
> 
>    if (line_end_event)   // --> is it an error?
>     begin
>     end
>    wait(line_end_event);  // --> is it an error?
> end
> 
> endmodule
> 
> SV allows 'null' to be assigned to named event. Considering that fact,
> wrt SV, is the case legal, because 'if (line_end_event)' can be read
as
> 'if (line_end_event != null)'.
> 
> --
> Regards
> Surya
> 
> 
> 
> 
> 
> --
> 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.
Received on Tue Mar 25 13:14:10 2008

This archive was generated by hypermail 2.1.8 : Tue Mar 25 2008 - 13:14:38 PDT