RE: SystemC exceptions and throw_it

John,

I agree with Philips here that the exceptions thrown can be arbitrary exceptions. The LRM could recommend that they be derived from std::exception but not mandate it.

For sc_unwind_exception, Philip's definition is fine - don't need sc_reset_exception though.

Thanks,
-Bishnupriya

class sc_unwind_exception

{

virtual bool is_reset() const = 0;

protected:

sc_unwind_exception();

sc_unwind_exception( const sc_unwind_exception& );

virtual ~sc_unwind_exception();

};

________________________________
From: john.aynsley@doulos.com [mailto:john.aynsley@doulos.com]
Sent: Tuesday, September 07, 2010 4:07 PM
To: Bishnupriya Bhattacharya; systemc-p1666-technical@eda.org
Subject: SystemC exceptions and throw_it

Bishnupriya, All,

1666-2005 has sc_report derived from std::exception, and for backward compatibility includes:

        typedef std::exception sc_exception;

Should we mandate or recommend that user-defined exceptions thrown by throw_it are derived from std::exception?

Would someone care to provide me with a definition of class sc_unwind_exception?

Thanks,

John A

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