Re: sc_port, sc_export binding overload and base classes

Hi Jerome,

>Maybe you misunderstood me, just have a look at one SystemC
implementation and class sc_port_b.

OK, I see what you are proposing now. When the current LRM was written,
there was a pretty strong agreement that sc_port_b was a feature of the
OSCI implementation, rather than a class that should be part of the
standard. You are correct that as it stands, operator()(sc_port<IF,N>&) in
the LRM does not reflect the way that the code is implemented in the OSCI
distribution or the behaviour described in clause 5.11.3. I still think
it would be better to find an alternative way to define the port-to-port
binding methods in the LRM rather than adding an additional class but I do
not feel strongly either way.

Regards,
Dave

-- 
Dr David Long 
Senior Consultant 
Doulos - Developing Design Know-how
VHDL * Verilog * SystemVerilog * SystemC * PSL * Perl * Tcl/Tk * Project 
Services
Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, 
UK
Tel:  + 44 (0)1425 471223                       Email: 
david.long@doulos.com 
Fax:  +44 (0)1425 471573                        http://www.doulos.com
--------------------------------------------------------------------------------
Doulos Ltd is registered in England and Wales with company no. 3723454
Its registered office is 4 Brackley Close, Bournemouth International 
Airport,
        Christchurch, BH23 6SE, UK. 
This message may contain personal views which are not the views of
Doulos, unless specifically stated.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.