Re: reset_signal_is variations

John, Kaz, all,

I think as well, that the interfaces should be consistent.

  Regarding my proposal, John is right that I had multiports in mind,
since with the Process Control Extensions multiple resets per process
are supported. Doing this manually as a user (by iterating through the
bound channels) is difficult due to the delayed binding.

  If multiple resets via a single port are not considered helpful, the
overload set

     void [async_]reset_signal_is(
        const sc_port<sc_signal_in_if<bool>,1>& port, bool level );
     void [async_]reset_signal_is(
        const sc_port<sc_signal_inout_if<bool>,1>& port, bool level );
     void [async_]reset_signal_is( const sc_signal_in_if<bool>&, bool );

would be sufficient to cover sc_in, sc_out and sc_inout.

  The functions taking a plain sc_signal_in_if<bool> are fine for direct
channel binding, since sc_signal_inout_if<bool> already inherits from
the input interface.

Greetings from Oldenburg,
Philipp

On 20/07/10 09:37, john.aynsley@doulos.com wrote:
> Kaz, All,
>
> If I understood Philipp correctly, he was proposing we support
> reset_signal_is for multiports. Here is Philipp's proposal
>
> "Regarding multi-ports for all variants, it would be enough to have
>
> template< typename N >
> void reset_signal_is( const sc_port<sc_signal_in_if<bool>,N>& port
> , bool level );
> template< typename N >
> void reset_signal_is( const sc_port<sc_signal_inout_if<bool>,N>& port
> , bool level );
>
> since sc_out<> is also derived from the generic inout port, right?
> An implementation of course could still drop the templates internally. "
>
> What does everyone think?
>
> John A
>
>
>
> From:
> Kaz Yoshinaga <yoshi@starc.or.jp>
> To:
> john.aynsley@doulos.com
> Cc:
> systemc-p1666-technical@eda.org
> Date:
> 20/07/2010 00:53
> Subject:
> Re: reset_signal_is variations
>
>
>
> Yes, sc_spawn_options should be extended.
>
> By the way, regarding the signal interface of reset_signal_is and
> async_reset_signal_is, don't they need to include inout interface as
> Philipp proposed?
>
> ie.
> void reset_signal_is( const sc_signal_inout_if<bool>& , bool );
>
> Regards,

-- 
Philipp A. Hartmann
Hardware/Software Design Methodology Group
OFFIS
R&D Division Transportation | FuE-Bereich Verkehr
Escherweg 2 · 26121 Oldenburg · Germany
Phone/Fax: +49-441-9722-420/282 · PGP: 0x9161A5C0 · http://www.offis.de/
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.