Re: [sv-bc] DataTypes: Proposed changes to section 5

Kathy,

Can we stop perpetuating the vectored and scalared keywords?

Bad enough that they exist, we don't have to keep mentioning them.

Shalom

On Tue, 9 Nov 2004, Kathy McKinley wrote:

> -----------------------------------------------------------------------------
> SECTION 5.1 Introduction:
>
> ADD TO END OF SECTION:
>
> SystemVerilog extends the set of data types that are available for modeling
> Verilog storage and transmission elements. In addition to the Verilog-2001
> data types, new predefined data types and user-defined data types can be
> used to declare constants, variables, and nets.
>
> -----------------------------------------------------------------------------
> SECTION 5.2 Data declaration syntax:
>
> ADD TO SYNTAX BOX:
>
> net_declaration ::=
> net_type_or_trireg [drive_strength|charge_strength] [vectored|scalared]
> data_type_or_implicit [delay3] list_of_net_decl_assignments;
>
>
> ----------------------------------------------------------------------------
> Add section called "Nets", right after section 5.4 Variables :
>
> A net declaration begins with a net type that determines how the values
> of the nets in the declaration are resolved. The declaration can
> optionally include drive or charge strength, a vectored or scalared
> indication, and delay values.
>
> Verilog-2001 restricts the data type of a net to a scalar, a bit vector,
> or an array of scalars or bit vectors. In SystemVerilog, any four-state
> data type can be used to declare a net. For example:
>
> trireg (large) logic #(0,0,0) cap1;
>
> typedef logic [31:0] addressT;
> wire addressT w1;
>
> wire struct packed { logic ecc; logic [7:0] data; } memsig;
>
> The data type of a net shall be one of the following:
>
> 1) A four-state integral type
>
> 2) An unpacked array or unpacked struct whose elements have data types
> that are allowed for a net
>
>
> -----------------------------------------------------------------------------
> SECTION 5.8.1 Equivalent types
>
> CHANGE:
>
> 4) A typedef for an enum, unpacked struct, or unpacked union, or a class
> is equivalent to itself and variables declared using that type within
> the scope of the type identifier.
>
> TO:
>
> 4) A typedef for an enum, unpacked struct, or unpacked union, or a class
> is equivalent to itself and to data objects that are declared using
> that data type within the scope of the data type identifier.
>

-- 
Shalom Bresticker                        Shalom.Bresticker @freescale.com
Design & Verification Methodology                    Tel: +972 9  9522268
Freescale Semiconductor Israel, Ltd.                 Fax: +972 9  9522890
POB 2208, Herzlia 46120, ISRAEL                     Cell: +972 50 5441478
  
[ ]Freescale Internal Use Only      [ ]Freescale Confidential Proprietary