• 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 Design
  3. analysis

Stats

  • Locked Locked
  • Replies 29
  • Subscribers 125
  • Views 22274
  • 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

analysis

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

    smlogan said:

    y1 = -40.0

    foreach(y1 '(27.0 150.0 -40.0)

     

     

    Shawn - this is absolutely unnecessary. SKILL doesn't require you to "declare" variables - and the type of a variable may change over time. In fact the foreach will cause a local variable y1 to be defined for the duration of the foreach - when the foreach completes, the previous value will become visible again (or if it was not defined, it will be unbound). That's fine...

    I looked at the latest code posted by Yen, and it works OK (I had to adjust it to reflect signal names in my own testcase ,but apart from that it worked fine).

    The most likely issue was that you may have accidentally had:

     temp (y1)

    rather than

     temp(y1)

    i.e. a space between the temp and the open parenthesis. This would have caused temp to be seen as a variable, followed by a function call to a function called y1. And that would result in:

    *Error* eval: unbound variable - temp
    *Error* load: error while loading file - "forum.ocn" at line 43

    Regards,

    Andrew.

     

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

    smlogan said:

    y1 = -40.0

    foreach(y1 '(27.0 150.0 -40.0)

     

     

    Shawn - this is absolutely unnecessary. SKILL doesn't require you to "declare" variables - and the type of a variable may change over time. In fact the foreach will cause a local variable y1 to be defined for the duration of the foreach - when the foreach completes, the previous value will become visible again (or if it was not defined, it will be unbound). That's fine...

    I looked at the latest code posted by Yen, and it works OK (I had to adjust it to reflect signal names in my own testcase ,but apart from that it worked fine).

    The most likely issue was that you may have accidentally had:

     temp (y1)

    rather than

     temp(y1)

    i.e. a space between the temp and the open parenthesis. This would have caused temp to be seen as a variable, followed by a function call to a function called y1. And that would result in:

    *Error* eval: unbound variable - temp
    *Error* load: error while loading file - "forum.ocn" at line 43

    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