Bishnupriya,
Re. dynamic events, you said in your original spec:
"To address this performance concern, the behavior of sc_event's default 
ctor after simulation start is kept unspecified, i.e. 
implementation-defined. An implementation may choose to treat such events 
exactly the same as static events, or it can choose to not name them at 
all, or somewhere in between."
In what sense to we want to allow "somewhere in between"? It would be fine 
to have some events named and others unnamed, but would we want an event 
that had a parent but no hierarchical name, or a hierarchical name and no 
parent? This would seem like an unnecessary complication to me. I would 
rather have each event either named or unnamed, where only named events 
have a parent, and no orphan has a name.
John A
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Nov 25 08:14:13 2010
This archive was generated by hypermail 2.1.8 : Thu Nov 25 2010 - 08:14:14 PST