• 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 clean all function loaded and global variable

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 15597
  • 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 clean all function loaded and global variable

CalenZoo
CalenZoo over 9 years ago

Dear all,

Do someone know to :

- "clean" all SKILL functions loaded?

- "clean" all gobal variables created ?

without exiting of virtuoso and restart everything....

Thank you in advanced,

Best regards,

Patrick

  • Cancel
Parents
  • liorscotland
    liorscotland over 9 years ago
    This is difficult, as you could have overridden some global variables, and procedures. So, you may "clear" everything, and end up not with what you have bargained for! The best choice would be to have what I call "strict practice", in which all of your variables and procedures have a naming convention, making removal very easy. Option 2 is to have at the very beginning a snapshot of procedures and variables, saved in a file. Then, dump a snapshot into a different file, and remove all that is the 2nd file and not in the first. The problem is that the code to do that would probably with be a new global needs removing, which can be done (you load a file to do that, last lines removing the newly defined procedures). You'll need to make sure that this happens BEFORE any of the codes that you want to track.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • liorscotland
    liorscotland over 9 years ago
    This is difficult, as you could have overridden some global variables, and procedures. So, you may "clear" everything, and end up not with what you have bargained for! The best choice would be to have what I call "strict practice", in which all of your variables and procedures have a naming convention, making removal very easy. Option 2 is to have at the very beginning a snapshot of procedures and variables, saved in a file. Then, dump a snapshot into a different file, and remove all that is the 2nd file and not in the first. The problem is that the code to do that would probably with be a new global needs removing, which can be done (you load a file to do that, last lines removing the newly defined procedures). You'll need to make sure that this happens BEFORE any of the codes that you want to track.
    • 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