• 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 Design
  3. leiHiCopy ?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 124
  • Views 13079
  • 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

leiHiCopy ?

archive
archive over 18 years ago

Can someone tell me what this function does and what arguments it requires?  What is an "\&_poiner"?

arglist => leiHiCopy(wtype \&_pointer t_string t_string t_string t_string t_string t_string t_string l_list "w&tttttttl")
Thanks!


Originally posted in cdnusers.org by m27315
  • Cancel
  • archive
    archive over 18 years ago

    This function is private, and is for internal use only - it's used inside the leHiCopy() code.

    There should be absolutely no need for you to use it, and as such I won't try to research what the arguments mean - if you were to use it, you'd be likely to hit migration problems if this function changed or was deleted.

    There is a good reason for certain functions to be private and undocumented - they are for internal use and are liable to change.

    So, what should you be using instead? If you want an interactive copy, use leHiCopy() ; if you want to do the copy procedurally, use dbCopyFig().

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Well, it never hurts to ask.  ;-)  Plus, I like to understand the underpinnings.  It helps me write better SKILL code.

    Thanks!


    Originally posted in cdnusers.org by m27315
    • 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