Seems to me if the context is wrong for the call, then the user is obviously
misusing the call. From a practical point, they cannot be executed
correctly, and thus not doing anything is a good move. From the user's
perspective, I think I would want it to be an error because it needs to be
corrected. If I issue a reset and it doesn't happen, it failed my
expectation and a warning seems to low. Warnings are for things you wouldn't
care about and can often ignore. Warnings are 'maybe a problem'.
On Wed, Dec 1, 2010 at 2:33 PM, <john.aynsley@doulos.com> wrote:
> 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* <http://www.mailscanner.info/>, 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 Wed Dec 1 13:01:10 2010
This archive was generated by hypermail 2.1.8 : Wed Dec 01 2010 - 13:01:12 PST