• 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. Can we pass value as variable to enterpath function other...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13419
  • 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

Can we pass value as variable to enterpath function other than pathWidth

Infy1
Infy1 over 16 years ago

 Hi,

Can we pass on a numerical value as a variable to enterPath function other than pathWidth .

 Regards,

Roy

  • Cancel
Parents
  • skillUser
    skillUser over 16 years ago

     Hi Roy,

     I'm not sure that I understand the question correctly. You want to pass a number to enterPath that is not for the path width argument? If so, what is this number for, what would it control or influence if not the path width?  Or are you asking if it is possible to use a variable for the pathWidth rather than a fixed numerical value?  In this case yes, a variable can certainly be used, for example:

    myWidth = 1.0

    procedure(myEPdone(win done pts)
     printf("DEBUG: win %L done %L pts %L\n" win done pts)
    )

    enterPath(
     ?prompts list("First point" "Next point")
     ?pathWidth myWidth
     ?doneProc "myEPdone")
     
     Here "myWidth" is a global variable though; one method to avoid creating too many global variables is to use the property list slot on an existing symbol, for example the symbol "myEPdone" is global because it is used to define a function.  A symbol has three slots available for use, a value slot (for use as variables), a function slot and a property list slot.  All three of these can co-exist on a symbol, so in this case, we could use the property list slot on myEPdone (or some other function name) for global storage that does not look global (at least SKILL Lint will not mark you down for it).  So the example could be changed slightly:
     
    myEPdone.width = 0.8
    enterPath(
     ?prompts list("First point" "Next point")
     ?pathWidth myEPdone.width
     ?doneProc "myEPdone")
     
    Not sure if it helps, if not, please clearly state what you are looking for.
     
    Regards,

    Lawrence.
     
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 16 years ago

     Hi Roy,

     I'm not sure that I understand the question correctly. You want to pass a number to enterPath that is not for the path width argument? If so, what is this number for, what would it control or influence if not the path width?  Or are you asking if it is possible to use a variable for the pathWidth rather than a fixed numerical value?  In this case yes, a variable can certainly be used, for example:

    myWidth = 1.0

    procedure(myEPdone(win done pts)
     printf("DEBUG: win %L done %L pts %L\n" win done pts)
    )

    enterPath(
     ?prompts list("First point" "Next point")
     ?pathWidth myWidth
     ?doneProc "myEPdone")
     
     Here "myWidth" is a global variable though; one method to avoid creating too many global variables is to use the property list slot on an existing symbol, for example the symbol "myEPdone" is global because it is used to define a function.  A symbol has three slots available for use, a value slot (for use as variables), a function slot and a property list slot.  All three of these can co-exist on a symbol, so in this case, we could use the property list slot on myEPdone (or some other function name) for global storage that does not look global (at least SKILL Lint will not mark you down for it).  So the example could be changed slightly:
     
    myEPdone.width = 0.8
    enterPath(
     ?prompts list("First point" "Next point")
     ?pathWidth myEPdone.width
     ?doneProc "myEPdone")
     
    Not sure if it helps, if not, please clearly state what you are looking for.
     
    Regards,

    Lawrence.
     
    • 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