RE: [sv-ec] "::" is ambiguous in parameterized classes

If there are bugs in the BNF, then let's fix them.  But there is nothing
wrong with my reasoning about what class_type currently allows.

-- Brad

-----Original Message-----
From: Rich, Dave [mailto:Dave_Rich@mentor.com] 
Sent: Friday, October 05, 2007 12:32 PM
To: Brad Pierce; SV_EC List
Subject: RE: [sv-ec] "::" is ambiguous in parameterized classes

Brad,

By that same reasoning, the BNF would not allow you to construct a class
passed as a type parameter class whatever_type; endclass

class A #(type B=whatever_type);
B b; // B is a type_identifier
function new();
	b = new();
endfunction
endclass

as well as a simple typedef

typedef whatever_type C; // C is a type_identifier according to the BNF
C c = new;

Clearly, a type_identifier can become whatever__type_identifier it needs
to be and would need to follow what ever rules need to be followed as
that type that it becomes.


Dave



> -----Original Message-----
> From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org]
On
> Behalf Of Brad Pierce
> Sent: Friday, October 05, 2007 11:06 AM
> To: SV_EC List
> Subject: RE: [sv-ec] "::" is ambiguous in parameterized classes
> 
> Mark writes --
> 
> >I do not see how this can be interpreted to already allow type 
> >parameters to be used to specify the base class.
> 
> The current BNF absolutely doesn't allow that.  A class_type requires
a
> class_identifier, which can only be declared with a class_declaration.
> 
> -- Brad
> 
> 
> --
> 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.