Stats

  • Locked Locked
  • Replies 10
  • Subscribers 144
  • Views 2828
  • 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

args _args

linbo

Can't find definitions or explanation of these two terms in cds documentation.  Could someone help (either with explanation or point me to documentation?)

 

Thanks in advance,

--lin

Parents
  • Hi Lin,

    In that specific case you may note that Andrew's method (the correct approach) used a userMenuTrigger and because it is a trigger function it will be supplied a dpl structure with information in it, but the code did not need any of this information so there was no access to the "args" structure/variable, so the argument is renamed to _args so that SKILL Lint does not complain about the function argument being supplied but not used.  In my code example I accessed the window id from the structure passed in, and so I did use "args" within the procedure body, so Lint would not have complained about that, hence no need for the underscore preceding the variable name.

    Hopefully this explains why for this example, but Andrew's earlier post was clear I thought too.

    Regards,

    Lawrence.
Reply
  • Hi Lin,

    In that specific case you may note that Andrew's method (the correct approach) used a userMenuTrigger and because it is a trigger function it will be supplied a dpl structure with information in it, but the code did not need any of this information so there was no access to the "args" structure/variable, so the argument is renamed to _args so that SKILL Lint does not complain about the function argument being supplied but not used.  In my code example I accessed the window id from the structure passed in, and so I did use "args" within the procedure body, so Lint would not have complained about that, hence no need for the underscore preceding the variable name.

    Hopefully this explains why for this example, but Andrew's earlier post was clear I thought too.

    Regards,

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