Stats

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

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?
Parents

  • SKILL uses eq() for checking identity, and equal() (aka "==") for checking equality.  You're talking about identity, but I want to check that two dbobjects have identical properties/attributes.  If they're eq(), then they definitely will, but if they're not eq(), they could still have equal attributes.  It would be cool if equal() and "==" did something like the forall() code in the OP.

Reply

  • SKILL uses eq() for checking identity, and equal() (aka "==") for checking equality.  You're talking about identity, but I want to check that two dbobjects have identical properties/attributes.  If they're eq(), then they definitely will, but if they're not eq(), they could still have equal attributes.  It would be cool if equal() and "==" did something like the forall() code in the OP.

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.