Re: reset_signal_is variations

John,

Thanks for the correction.
It was my misreading and I withdraw that.

Best regards,
Kaz

(2010/07/20 16: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,
> --
> Kaz Yoshinaga
>
> (2010/07/16 1:25), john.aynsley@doulos.com wrote:
> > systemc-2.3.10dec09_beta has the following methods in class sc_module
> >
> > void reset_signal_is( const sc_in<bool>& , bool );
> > void reset_signal_is( const sc_inout<bool>& , bool );
> > void reset_signal_is( const sc_out<bool>& , bool );
> > void reset_signal_is( const sc_signal_in_if<bool>& , bool );
> >
> > void async_reset_signal_is( const sc_in<bool>& , bool );
> > void async_reset_signal_is( const sc_inout<bool>& , bool );
> > void async_reset_signal_is( const sc_out<bool>& , bool );
> > void async_reset_signal_is( const sc_signal_in_if<bool>& , bool );
> >
> > whereas class sc_spawn_options only contains the following subset:
> >
> > void reset_signal_is( const sc_signal_in_if<bool>& , bool );
> > void reset_signal_is( const sc_in<bool>& , bool );
> >
> > void async_reset_signal_is( const sc_signal_in_if<bool>& , bool );
> > void async_reset_signal_is( const sc_in<bool>& , bool )
> >
> > Do we want to extend sc_spawn_options to include the methods for
> > sc_out and sc_inout?
> >
> > 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* <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.