• 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. Scope form name variable

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 145
  • Views 15654
  • 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

Scope form name variable

psill000
psill000 over 12 years ago

When I create a GUI with hiCreateAppForm and run lint on the script I get global variables from the form name. 

Is there a good way of scoping the variable so I don't get a Lint warning of global variable error.

Currently I have the GUI in a different file to lessen the global warning errors.

 

Paul

  • Cancel
Parents
  • skillUser
    skillUser over 12 years ago

     Hi Paul,

    Well, a form symbol has to be global, so you can't avoid that, but what you can do is to make sure that it is named with an appropriate prefix (e.g. PS or MY etc.), and then on the Lint form you enter this for the package prefixes - this should allow Lint to recognise that these are required globals but have the appropriate prefix and so should not reduce your score.

    Hope this helps!

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 12 years ago

     Hi Paul,

    Well, a form symbol has to be global, so you can't avoid that, but what you can do is to make sure that it is named with an appropriate prefix (e.g. PS or MY etc.), and then on the Lint form you enter this for the package prefixes - this should allow Lint to recognise that these are required globals but have the appropriate prefix and so should not reduce your score.

    Hope this helps!

    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