AOP needs OOP. OOP needs generics. It ain't one or the other.
e had OOP-style inheritance as well as AOP-style inheritance. OOP languages make heavy use of "generics" in the form of type parameters (e.g. C++ templates). OOP without the ability to parameterize types was really clunky, because you ended up hacking the necessary flexibility re. types by casting void pointers.
John A
-----owner-vhdl-200x@eda.org wrote: -----
To: "vhdl-200x@eda.org" <vhdl-200x@eda.org>
From: Jim Lewis
Sent by: owner-vhdl-200x@eda.org
Date: 03/17/2011 10:29PM
Subject: [vhdl-200x] Why OOP vs Generics
Hi,
Martin asked a question in this mornings meeting:
why generics vs OOP/AOP programming? What are some
examples where we need OOP/AOP over using generics?
Particularly for testbenches.
I would like to open/provoke the discussion from there.
Best,
Jim
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jim Lewis Director of Training mailto:Jim@SynthWorks.com SynthWorks Design Inc. http://www.SynthWorks.com 1-503-590-4787 Expert VHDL Training for Hardware Design and Verification ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 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 Fri Mar 18 12:56:22 2011
This archive was generated by hypermail 2.1.8 : Fri Mar 18 2011 - 12:56:41 PDT