Stats

  • Locked Locked
  • Replies 12
  • Subscribers 64
  • Views 20942
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Modularization of SystemVerilog

archive

Hi guys,

I have an question concerning modularization, but I have not found it in one of the following books: "Writing Testbenches using SystemVerilog" and "SystemVerilog for Verification". So, I hope you can help me.

I have written much classes, which are all in ONE file so far, but this is not the target state I wish for this project. The problem is, that for example, one class instantiates another class and I don't know, how to separate the classes.

Is a mechanism available, as C-Header-Files?

I hope you can help me, because several smaller files are much better than one singe huge file.

Thanks for your help!
If the answer should be in one of the itemized books, please sorry, I haven't found it!

Sebastian


Originally posted in cdnusers.org by sebastian
Parents

  • Dave answered the question about partitioning up the classes into smaller packages. That is definitely the way to go and then you can "import" the packages you need into the modules. Of course you will need to make sure that you pass the package files to the compiler before the modules that need to import them. I think you may have also asked about how to call a class that hasn't been defined in another class. The way to do that is to use typedef as in this example: typedef class future_c; class current_c; future_c f; ... endclass class future_c; ... endclass The class future_c can be in the same file as current_c or in another file as long as both classes are visible to the compiler during the same compilation run. Tim


    Originally posted in cdnusers.org by tpylant
Reply

  • Dave answered the question about partitioning up the classes into smaller packages. That is definitely the way to go and then you can "import" the packages you need into the modules. Of course you will need to make sure that you pass the package files to the compiler before the modules that need to import them. I think you may have also asked about how to call a class that hasn't been defined in another class. The way to do that is to use typedef as in this example: typedef class future_c; class current_c; future_c f; ... endclass class future_c; ... endclass The class future_c can be in the same file as current_c or in another file as long as both classes are visible to the compiler during the same compilation run. Tim


    Originally posted in cdnusers.org by tpylant
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.