• 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. Custom IC SKILL
  3. Equality of dbObjects

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 15295
  • 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

Equality of dbObjects

tweeks
tweeks over 13 years ago

Are dbobjects ever equal?

I did a test, creating two labels that are exact copies of eachother: same lpp, same xy, etc. Watch what happens:

> forall(prop label1->? get(label1 prop) == get(label2 prop))
 t
> label1 == label2 
 nil 

Looks like equality is not implemented for labels?

  • Cancel
Parents
  • dmay
    dmay over 13 years ago

    No, they are never equal and I wouldn't expect them to be equal. If I changed one of those two labels, I would not want the other one to change. When you copied the first, you requested a separate object.

    If the variable label1 and the variable label2 referenced the same physical label object, then they would be equal. But by using copy, you requested a second object.

    Derek 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 13 years ago

    No, they are never equal and I wouldn't expect them to be equal. If I changed one of those two labels, I would not want the other one to change. When you copied the first, you requested a separate object.

    If the variable label1 and the variable label2 referenced the same physical label object, then they would be equal. But by using copy, you requested a second object.

    Derek 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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