sc_event_and/or_list

Tor, All,

I think we have a consensus that we want to make the change such that
sc_event_and/or_list can be instantiated as proper objects and act as
containers for events that can be passed to wait() and next_trigger() (at
least).

Would you (or someone else) please make a specific proposal for classes
sc_event_and_list and sc_event_or_list to go into the LRM. I started
prototyping this months back and ran into some C++ issues. As I recall
from my experiments, the prototype wait(sc_core::sc_event_or_list&)
currently precludes having something like wait(all_events()); where
all_events() returns an event list by value. So we need a set of
signatures for the constructor(s)/operators of the event list classes that
work with the current signatures of wait/next_trigger.

John A

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