• 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. mandatory keyed attribute

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 142
  • Views 12923
  • 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

mandatory keyed attribute

Aritra
Aritra over 13 years ago

Hi ,

     How to set a mandarory keyed attribute in procedure ? If I use "@key" before any attribute it automatically becomes an optional one. In some inbuilt form functions (like hiCreateAppForm ?name is mandatory keyed field) it exists. Can we make something similar for our use ?  

  • Cancel
Parents
  • skillUser
    skillUser over 13 years ago

     Hi Aritra,

    One way that you could emulate the behaviour of hiCreateAppForm's requirement of a key parameter is to give the parameter a known unwanted (bogus) default value and then test for this value in the procedure body, something like the following example:

    
      procedure(CCFprocTest(@key (requiredParam 'notSupplied))
    when(requiredParam=='notSupplied
    error("CCFprocTest: required parameter 'requiredParam' was not supplied")
    ); when
    ...
    ); procedure

     You could alternatively check against the 'unbound symbol - if the parameter is unbound it was not supplied (test using boundp() ) and perhaps set the parameter internally to a desired default value if this is not truly an error condition.

    I hope that this helps you.

    Regards,

    Lawrence.

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

     Hi Aritra,

    One way that you could emulate the behaviour of hiCreateAppForm's requirement of a key parameter is to give the parameter a known unwanted (bogus) default value and then test for this value in the procedure body, something like the following example:

    
      procedure(CCFprocTest(@key (requiredParam 'notSupplied))
    when(requiredParam=='notSupplied
    error("CCFprocTest: required parameter 'requiredParam' was not supplied")
    ); when
    ...
    ); procedure

     You could alternatively check against the 'unbound symbol - if the parameter is unbound it was not supplied (test using boundp() ) and perhaps set the parameter internally to a desired default value if this is not truly an error condition.

    I hope that this helps you.

    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