Bishnupriya,
The spec says "Throwing an exception in a process that has not started 
execution yet shall have no effect for the same reasons as above, and 
shall be an error. Setting up the include_descendants flag has no 
associated semantics in this case, because the throwee process is 
guaranteed to not have any descendants, as it has never executed, and 
hence, has never spawned any children"
However, if you remember, we decided that calling throw_it on a method 
process is allowed and has no effect except that an implementation may 
issue a warning. Would it not be more consistent to apply this same rule 
in the case of calling throw_it before simulation has started? As the 
rules stand, we have the situation that
- calling throw_it on a method process during elaboration is an error
- calling throw_it on a method process during simulation but before the 
associated function has first executed is allowed, but may cause a warning
Thanks,
John A
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Sep 1 06:47:37 2010
This archive was generated by hypermail 2.1.8 : Wed Sep 01 2010 - 06:47:38 PDT