• 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. mapping symbol list to a value list

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 14234
  • 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

mapping symbol list to a value list

cessej
cessej over 14 years ago

I want to map a symbol list into a value list. It looks simple base on sklangref.pdf but it doesnt work as expected.

********************************************

symbolList=list('cv 'bBox 'layer)

valueList=list(geGetEditCellView() list(0:0 10:10) list("M1" "drawing"))

mapcar(lambda((x y) set(x y)) symbolList valueList)

println(cv) ;; doesn't print the result of geGetEditCellView()

println(bBox) ;; it doesnt print list(0:0 10:10)

println(layer) ;; it doesn't print list("M1" "drawing")

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

    Several of the forms which deal with variable access and evaluation have alternative forms to allow them to cope with the different binding rules in SKILL++. For example, set(), symeval(), eval(), and so on. This is because they wouldn't otherwise know whether you were trying to refer to a SKILL dynamically scoped variable or a SKILL++ lexically scoped variable - and hence they need to know which SKILL++ environment is active - so you pass theEnvironment() to solve this. This is covered in the SKILL++ documentation (in the Language User Guide, if my memory is correct; not at work today), so definitely worth reading.

    Regards,

    Andrew.

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

    Several of the forms which deal with variable access and evaluation have alternative forms to allow them to cope with the different binding rules in SKILL++. For example, set(), symeval(), eval(), and so on. This is because they wouldn't otherwise know whether you were trying to refer to a SKILL dynamically scoped variable or a SKILL++ lexically scoped variable - and hence they need to know which SKILL++ environment is active - so you pass theEnvironment() to solve this. This is covered in the SKILL++ documentation (in the Language User Guide, if my memory is correct; not at work today), so definitely worth reading.

    Regards,

    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