Re: [sv-ac] Items would like to address at upcoming meetings

*16.14.6 Sequence methods // .triggered need further clarification*
http://www.eda-stds.org/svdb/view.php?id=3552
Made some updates
I got the following responses from a responsible party on some questions:
1) wire trig = a_then_b.triggered; // Useful?? Legal??
Should be legal (although I am not sure how useful this is). ‘trig’ should
go high in the Observed region when sequence ‘a_ten_b’ is evaluates to true
and then go low in the next time tick.

2) Also, Is anything.triggered really defined as an "event" in the LRM?
A named sequence can be used as an event (Sec 9.4.2.4) – anytime you want to
use it as an event you should use @(<named_sequence>).
In some simulators @(<named_sequence>.triggered) behaves same as
@(<named_sequence>.
 If used as @(<name_sequence>.triggered) that would trigger twice similar
to @(trig).

Comments?
Ben

On Wed, May 11, 2011 at 4:30 PM, ben cohen <hdlcohen@gmail.com> wrote:

> Dmitry,
> Below is a list of items I would like us to address:
> *Make drivers of inout ports accessible*
> http://www.eda-stds.org/svdb/view.php?id=3478
> Uploaded a new version of the mantis.
> I also uploaded a diagram (extdriver.pdf) clarifying the meaning of those
> functions in a DUT instantiated in a testbench.
>
> *16.14.6 Sequence methods // .triggered need further clarification*
> http://www.eda-stds.org/svdb/view.php?id=3552
> Made some updates
>
> Local Variables Flow Out Issue in and/or/intersect/implies
> http://www.eda-stds.org/svdb/view.php?id=3195
> Made some updates
>
> I also welcome comments on these topics.
> Ben Cohen SystemVerilog.sv
>

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