how does Interface Wrapper promote re use / ease of use of interface class

最新推荐文章于 2019-01-01 17:01:36 发布

naclkcl9

最新推荐文章于 2019-01-01 17:01:36 发布

阅读量1.9k

点赞数

分类专栏： SystemVerilog 文章标签： interface wrapper construction class table each

本文链接：https://blog.youkuaiyun.com/naclkcl9/article/details/7244006

版权

SystemVerilog 专栏收录该内容

83 篇文章

订阅专栏

本文探讨了在System Verilog中通过Wrapper Class嵌入接口，利用工厂模式选择不同Wrapper Class，从而实现接口类的更好重用性和简化配置的方法。此外，介绍了几种替代方案，如在构造时传递接口、使用查找表控制接口选择等。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

My question is how does it help / add value to have the virtual interface in a wrapper class and initialize / configure using vmm_opts related code ?

In summary , how does Interface Wrapper promote re use / ease of use of interface class ?

Currently, systemverilog interfaces are not extensible.
Therefore once you have picked one you are stuck and cannot modify it/add a signal/ change a signals defualt value etc.
If you embed the interface within a wrapper-class you canuse the factory to select which wrapper-class you use.
and each wrapper class can have a different interface embedded within it.
Thus, you get better reuse.

There are several alternatives such as passing the interface to all objects that require them at time of construction, allowing you to pass a different interface as a class-parameter.
or use a lookup table where you store the interface and the objects get the interface from the look-up table and yuo can control the interface that is set in the lookup table.
etc