Re: Empty events lists

I think my point needs some elaboration.

> If we think semantically, an empty sc_event_and_list should be equivalent to
> waiting for an event that triggers immediately -- more like
> wait(SC_ZERO_TIME).

Say we are programming at a meta-level, by creating a script (in
python, or using template meta-programming) and we have a situation
where a variable number of events are gating some process (in a
logically anded fashion). Now think of a situation where such a gating
event list is empty. Now that there are no gating events, we should
execute the process immediately.

> And an sc_event_or_list should be equivalent to waiting
> for an event that never happens -- practically closer to wait(SC_MAX_TIME).

This would be a situation where a variable number of events are
enabling a given process. This corner case would be where no enabling
event is present and the process therefor does not get a chance to
execute. So we keep waiting.

> But does this make sense? Maybe in some situations where the SystemC code is
> outputted by a code generator?

> Regards
> - Puneet
> --
> CoVerify Systems Technology

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