RE: sc_report::get_verbosity()

Yes, that could be fine too. So that essentially means the user should first check the severity of the sc_report and only if SC_INFO, then pay any attention the verbosity value. Works for me.

Thanks,
-Bishnupriya

From: john.aynsley@doulos.com [mailto:john.aynsley@doulos.com]
Sent: Monday, January 17, 2011 10:23 PM
To: Bishnupriya Bhattacharya
Cc: P1666 Technical WG
Subject: Re: sc_report::get_verbosity()

Bishnupriya,

Good point. Since the implementation is obliged to ignore the verbosity if the severity is not SC_INFO, would it be better for the value returned from get_verbosity to be undefined?

John A

From:

Bishnupriya Bhattacharya <bpriya@cadence.com>

To:

"john.aynsley@doulos.com" <john.aynsley@doulos.com>

Cc:

P1666 Technical WG <systemc-p1666-technical@eda.org>

Date:

17/01/2011 16:40

Subject:

sc_report::get_verbosity()

________________________________

John,

I just noticed this issue. Sorry for the late notice. LRM says

"int get_verbosity() const;
const char* get_file_name() const;
int get_line_number() const;
Each of these six member functions shall return the corresponding property of the sc_report object.
The properties themselves can only be set by passing their values as arguments to the function
sc_report_handler::report."

The verbosity property is only defined for SC_INFO messages. What should sc_report::get_verbosity() return for non-info messages? We could specify a default value of SC_MEDIUM (200) as the verbosity property of non-info reports - something needs to be spelled out in the LRM.

Thanks,
-Bishnupriya

----------------------------------------------------------------------------------------------------------------------------------------------------
    Bishnupriya Bhattacharya | Software Architect - Virtual System Platform | Cadence
    P: +91.80.4184.1197 www.cadence.com<http://www.cadence.com/>
----------------------------------------------------------------------------------------------------------------------------------------------------

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