• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. access to distint unit data member ...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 13100
  • 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

access to distint unit data member ...

archive
archive over 17 years ago

i've got a question which is not essential, but still can prevent redefinision in my code. i'd like to use a port in my struct, which is previously defined in another unit. the current hierarchy is as follows : sys.struct sys.unit perhaps i should include my struct from the unit, so i could have access to this data member...


Originally posted in cdnusers.org by zcabeli11
  • Cancel
  • archive
    archive over 17 years ago

    Hi,

    It' s not recommended to place your components directly under sys, but technically speaking you could access the port simply by giving the full path (sys.xxx...)
    Better alternatives would be to create a parent-son hierarchy (like you suggessted) or interconnect the two by pointers ("brothers"). The chosen topology depends on your application.

    Yaron





    Originally posted in cdnusers.org by thinkverification
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information