reset_signal_is

There have been several enhancement requests regarding reset_signal_is:

* There is no reset_signal_is( const sc_signal<sc_logic>&, bool). If
clocking can be specified via an sc_signal<bool> or sc_signal<sc_logic>,
the reset should be specifiable in the same terms. A counter-argument is
that sc_clock is derived from sc_signal<bool>, so using <bool> for resets
is consistent.

* The LRM specifies 2 signatures for reset_signal_is

  void reset_signal_is( const sc_in<bool>& , bool );
  void reset_signal_is( const sc_signal<bool>& , bool );

The 4feb06 kit implements the following 2 signatures

   void reset_signal_is( const sc_in<bool>& port, bool level );
   void reset_signal_is( const sc_signal_in_if<bool>& iface, bool level );
<---------- this is a superset of what the LRM says

Should the LRM be modified (in the future) to allow the superset that the
4feb06 kit allows?

* We'd like to specify more than one "reset_signal_is" for one SC_THREAD.
 
[The Cadence process control spec supports multiple reset_signal_is()
specification for a single thread (Section 2.8.3).]

*.The syntax for asynchronous reset should be defined in LRM.
[The Cadence process control spec adds asynch_reset_signal_is() and
sync_reset_on/off]

Comments on any or all of the above?

Thanks,

John A

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