RE: [vhdl-200x] VHDL Testbench Enhancements

Tim,
- methods (functions/tasks/procedures) that operate on the objects
Agree.

- inheritance (extensions of previously defined objects into new
objects, derived from the original)
Good point. I overlooked inheritance and polymorphism. Are we going to
support single inheritance (like Java), or multiple inheritance (C++)?

Jim,
> For a type this only requires extending ports to allow shared
variables.
I am not too sure how shared variables play a role in the OO scene. I
have yet to read the documentation on this proposal. Maybe some
explanation would help. :)

> Classes need to be core language features so they can extend the type
system and preserve the type safety of the language, not break it.
> Since randomization needs a container and it would be convenient if
that container were a class (due to the OO), it would be advantageous to
specify both classes and randomization in the same standard.
Agreed.

Regards,
Daniel

-----Original Message-----
From: owner-vhdl-200x@eda.org [mailto:owner-vhdl-200x@eda.org] On Behalf
Of Tim Schneider
Sent: Saturday, May 26, 2007 12:16 AM
To: vhdl-200x@eda.org
Subject: RE: [vhdl-200x] VHDL Testbench Enhancements

 

>>ports. The only issues are how to add another layer of 
>>abstraction which defines the security of the attributes (or 
>>signals, components, etc.) that are contained within the 
>>entity-architecture body, somewhat like public, protected, or 
>>private attributes in object-oriented languages.

Daniel, 

re: OOP with VHDL

two other issues maybe three?

- methods (functions/tasks/procedures) that operate
on the objects

- inheritance (extensions of previously defined objects
into new objects, derived from the original)

- handles/pointers to objects 

I've seen linked list implementations in VHDL
so the third one can be done within the constraints
of the existing language, dont know about the 
first two.

An extension may be the way to go, without totally 
redefining the current language syntax.  So then which
language does one choose as an extension?  C++?, maybe
the System C flavor of it?  System Verilog?  Open Vera?
'E'?  

The way these languages currently tie into VHDL 
is left as an exercise for the EDA vendors to implement
and they're all different.  Perhaps the route is through
the current VHPI?


 -tim


Synopsys Inc.


-- 
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.