• 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. How to find functions' definition in cadence?

Stats

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

How to find functions' definition in cadence?

Renee
Renee over 15 years ago

Hi,

 I try to find the definition of a function called getSGq( ) in cdsFinder and other user manuals , but there are no results. I wonder how and where can I find information about this kind of function.

 Thanks in advance!

 Lei 

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

    Part of the reason why getSGq is a bit of a special case is that the idea is that we document it being used as an operator ~> but not in its functional form. Since all operators in SKILL are functions, this is a bit of an oddity - and for those of us that write LISP-style code, rather an anomoly. Probably we should just go ahead and document it properly and have done with it! I do remember a discussion about it a few years ago, where we decided that most users would use the ~> form and so documenting it was a bit excessive.

    Regards,

    Andrew.

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

    Part of the reason why getSGq is a bit of a special case is that the idea is that we document it being used as an operator ~> but not in its functional form. Since all operators in SKILL are functions, this is a bit of an oddity - and for those of us that write LISP-style code, rather an anomoly. Probably we should just go ahead and document it properly and have done with it! I do remember a discussion about it a few years ago, where we decided that most users would use the ~> form and so documenting it was a bit excessive.

    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