RE: Errors from process control methods

All,

The thing is, if we made(e.g) reset() or kill() to be errors during a pause, why would they not be errors before the start of simulation? It seems rather ad hoc.

John A

-----Bishnupriya Bhattacharya <bpriya@cadence.com> wrote: -----
To: "john.aynsley@doulos.com" <john.aynsley@doulos.com>, "systemc-p1666-technical@eda.org" <systemc-p1666-technical@eda.org>
From: Bishnupriya Bhattacharya <bpriya@cadence.com>
Date: 12/02/2010 08:44AM
Subject: RE: Errors from process control methods

    
John,
 
Good catch. I would prefer a warning over error, but can also live with an error.
 
Thanks,
-Bishnupriya
 
   
From: john.aynsley@doulos.com [mailto:john.aynsley@doulos.com]
Sent: Thursday, December 02, 2010 2:03 AM
To: Bishnupriya Bhattacharya; systemc-p1666-technical@eda.org
Subject: Errors from process control methods

    
Bishnupriya, All,

I have just noticed an inconsistency. When discussing sc_pause, we recently decided "it shall be an error" to call kill, reset, or throw_it while simulation is paused. But a while back, after some discussion, we decided that calling such methods from the wrong context, such as during elaboration, would not be an error but would have no effect other than optionally generating a warning.

So my question is, should the same apply when paused, i.e just an optional warning?

Thanks

John A

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