The second derivation rule of a nettype declaration is to create another name for an existing nettype. However I believe it applies to user defined nettypes only.
net_type_declaration ::= // from A.2.1.3
nettype data_type net_type_identifier
[ with [ package_scope | class_scope ] tf_identifier ] ;
| nettype [ package_scope | class_scope ] net_type_identifier net_type_identifier ;
-----Original Message-----
From: Daniel Mlynek [mailto:danielm@aldec.com.pl]
Sent: Monday, December 05, 2011 9:39 AM
To: Francoise Martinolle
Cc: sv-bc@eda.org
Subject: Re: [sv-bc] nettype
No i want simple feature equals to what can I do for data types.
Ie I want do declare a net with a data type and predefined net type
wire logic [3:0] w;
Assume that I'm using such pair in many places and I want to change the net type - to do so I would have to find each interesting occurrence and do the change is I could :
typedef_net wire mynet;
typedef reg[3:0] mytype;
mynet mytype w;
then all I need to do is to change mynet declaration.
Same idea like for types
DANiel
On 12/5/2011 3:26 PM, Francoise Martinolle wrote:
> I am trying to understand what you want to achieve.
> Do you want to "redefine' the already predefined nettype "wire" and
> use its predefined resolution for the logic datatype?
>
> Francoise
> '
>
> -----Original Message-----
> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
> Daniel Mlynek
> Sent: Wednesday, November 30, 2011 3:09 AM
> To: sv-bc@eda.org
> Subject: [sv-bc] nettype
>
> sv2012 adds nettype: mantis: 3398 . Extension define in this mantis add more possibilities but I was thinking about smth simpler.
> Now I do not have a way to define smth like typedef on net_type to achieve declaration like:
>
> typedef_net wire mynet;
> typedef reg[3:0] mytype;
> mynet mytype w;
>
> mantis 3398 will also wont help me.
>
> DANiel
>
>
> --
> This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
>
>
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Dec 5 06:46:40 2011
This archive was generated by hypermail 2.1.8 : Mon Dec 05 2011 - 06:46:46 PST