Jump to content

Inter modules communciation


manuelselva

Recommended Posts

Hi,

 

In my systemc design, I am making high level abstractions about my system. I am not considering at all the time required to transfert information from one module to another. In this case, what are the arguments of not using "standard C++" communication means to let my modules exchange this information ? Do these arguments exist meaning that it's better choiche to go to ports and channels even in this case ?

 

Thank you for your help,

 

-----

Manu

Link to post
Share on other sites

I guess the main advantage of using SystemC is that ports/modules/channels give you a standard approach. Even if you don't care about time passing, you may well care about the order that things happen in, and then events and time are still useful. Also of course you get a ready to use threading library and scheduler.

 

The disadvantage might be simulation speed compared to pure C++. And of course you have to learn SystemC.

 

The main advantage of C++ is that you can do exactly what you want (you're free!)

The main disadvantage of C++ is that you can do exactly what you want :-) (You're re-inventing the wheel)

 

regards

Alan

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...