Hi Puneet,
This does not make sense to me either. A wait(SC_ZERO_TIME) does not
trigger immediately - it wakes up in the next delta cycle.
Also, why should an emply OR list wait forever while an empty AND list
never waits? If you wanted to have semantics like this, shouldn't it be
the OR that wakes up immediately rather than the AND?
Dave
From:
Puneet Goel <p.goel@acm.org>
To:
david.long@doulos.com
Cc:
john.aynsley@doulos.com, "Philipp A. Hartmann"
<philipp.hartmann@offis.de>, owner-systemc-p1666-technical@eda.org,
systemc-p1666-technical@eda.org
Date:
02/11/2010 10:04
Subject:
Re: Empty events lists
Sent by:
owner-systemc-p1666-technical@eda.org
Greetings
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). And an sc_event_or_list should be equivalent to
waiting for an event that never happens -- practically closer to
wait(SC_MAX_TIME).
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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Nov 2 03:29:02 2010
This archive was generated by hypermail 2.1.8 : Tue Nov 02 2010 - 03:29:03 PDT