Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13603
  • 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

let-statement including hiDisplayForm

mschw

Hello,

in this example on support.cadence.com is shown how a form with an editable ReportField can be created. Within the procedure CCSEditReportForm() the form gets displayed , using the command hiDisplayForm(form). When I put  CCSEditReportForm() in the CIW the form will pop up. I observed that both local parameters reportField  and form of procedure  CCSEditReportForm() - which are included in a let statement - are global. For instance when the form is visible and i put  reportField  in the CIW I get e.g. reportStruct@0x21a26b48 as a return value.

My expectation would be that reportField  shouldn't be globally visible since it's included in the let statement ?!

Many thanks.

Kind regards,

Matthias

Parents

  • Hi Matthias,

    What you're seeing is SKILL's dynamic scoping. In this example the call to hiDisplayForm is within the function CCSEditReportForm, and because the hiDisplayForm call is blocking, at the point it is called the scope is still within the let within CCSEditReportForm. Because of that, the "local" variables are still visible (you can think of each variable as being like a stack when in SKILL mode (not SKILL++ though, which uses lexical scoping)). So the variables will be visible until that scope ends (the let returns).

    If you add ?dontBlock t into the arguments of the hiCreateAppForm, then hiDisplayForm will return as soon as the form is display, and then the let() will return too, and so the reportField variable will no longer be in scope - and so won't be visible when you type reportField in the CIW.

    Regards,

    Andrew

  • in reply to Andrew Beckett

    Hi Andrew,

    thanks for the detailed explanation.

    Regards,

    Matthias

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