• 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. symbol property question

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 14436
  • 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

symbol property question

RVERP
RVERP over 12 years ago

I declare 3 variables

a = 10
b= 20
test=list('a 'b)

now I do test->x = 99

now test = (a x 99 b)

 So my list has become 4 items long, containing symbols a,b and x, and a value 99
x is still unbound.

 what has happened when i did test->x = 99??

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    There is absolutely no problem with having a disembodied property list with something other than nil as the first element - in fact I have used this to allow me to store something useful in that place - to allow me to have assoc lists of dpls.

    The DPL will work fine - you can use test->x to retrieve the value. The fact that there is a strange dummy value at the end wouldn't be a problem. Not sensible, but not a problem either.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    There is absolutely no problem with having a disembodied property list with something other than nil as the first element - in fact I have used this to allow me to store something useful in that place - to allow me to have assoc lists of dpls.

    The DPL will work fine - you can use test->x to retrieve the value. The fact that there is a strange dummy value at the end wouldn't be a problem. Not sensible, but not a problem either.

    Andrew.

    • 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