• 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. Multiple Classes per Package

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 13614
  • 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

Multiple Classes per Package

archive
archive over 18 years ago

Do I need to declare every class in a separate package or can I place multiple classes in a single package?

Dave Fechser
LSI Logic, Inc.
Fort Collins, CO


Originally posted in cdnusers.org by dfechser
  • Cancel
  • archive
    archive over 18 years ago

    Hello Dave,

    You are free to place multiple classes into a single package.

    Kathleen


    Originally posted in cdnusers.org by kameade
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    I hope this is not a language related question - LRM doesn't limit any such thing. As a methodology as well I will be very surprised if someone tries that - we are only populating the namespace by doing that. Instead what we usually do in our company and also recommend to our customers is to have one package per IP block - such as AHB, ENET, PCI etc. Sure there can be few packages per complex IP if needed but not 1 package per class.

    Regards
    Ajeetha, CVC
    www.noveldv.com  


    Originally posted in cdnusers.org by ajeetha
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Thanks. I want to do one package per VIP block but have only been able to find examples of one-class-per-package.


    Originally posted in cdnusers.org by dfechser
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Example:

    package vip_pkg;

    class one_c;
    ...
    endclass

    class two_c;
    ...
    endclass

    endpackage

    module vip;

    import vip_pkg::*;

    endmodule


    Originally posted in cdnusers.org by tpylant
    • 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