• 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 print name of passed parameter

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 7081
  • 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 print name of passed parameter

Brad RFeng
Brad RFeng over 2 years ago

Hi,

I need to print the name of a variable/object passed to a skill procedure from an ADE output expression. In this simple example Pout_dBm is passed to myFunc(). The desired print statement would result in "passed signal = Pout_dBm". 

procedure( myFunc(arg)
    printf("here\n")
    ;;printf("passed signal = %s\n" arg) ;; how to make this work?
    ;;calculation
);;myFunc

Regards,

Brad

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago

    The only clean way of doing this is to define it as a macro:

    defmacro(myFunc (arg)
      printf("passed signal = %L\n" arg)
      `(2*,arg)
    )

    For example:

    adb=23
    myFunc(adb)
    passed signal = adb
    46

    You may need to read up on macros to figure out the syntax (be careful though - overusing macros can lead to unclear code).

    The idea is that a normal function evaluates all its arguments before it is called, so can't know the name of a variable or the expression passed to it. Macros however are passed the actual code in their arguments and can see that, and are expected to return the transformed expression to evaluate; if called as a normal function, they would also invoke the resulting expression.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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