• 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. Allegro X PCB Editor
  3. Local variables to multiple procedures in an il file

Stats

  • Replies 6
  • Subscribers 160
  • Views 14869
  • Members are here 0
More Content

Local variables to multiple procedures in an il file

skillnewbie
skillnewbie over 16 years ago

Hi,

I have an il file which consists of two procedures, it looks like this:

procedure( myProcedureA()

                let((varA varB)

                     procedureB()

                   ) )

procedure( myProcedureB()

                let((varC varD)

                     skill coding...

                   ) )

in this case, varA and varB belong to prcedureA while varC and varD belong to procedureB.

after either procedureA or B is executed, they become "unbound", which means at Skill Shell, we type

"Skill> println(varA) " we shall get an "unbound variable" message.

 

I want to have a glabal variable (that's say varE) which can be shared by both procedures A and B,

However, I want to make it local to A and B only, which means after A and B are executed (since A will call B),

when we type "Skill> println(varE)" it shall produce an "unbound variable" message. 

 

How shall I go with it? Thanks~

  • Sign in to reply
  • Cancel
  • Anton
    Anton over 16 years ago

     Hello,

    You can have varE in the let statement for myProcedureA, and then passed as an argument to myProcedureB:

     
    procedure( myProcedureA()

                    let((varA varB varE)

                         procedureB(varE)

                       ) )

    procedure( myProcedureB(varE)

                    let((varC varD)

                         skill coding...

                       ) )

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • eDave
    eDave over 16 years ago

    You're in luck. You don't need to do anything. The local variables in the calling procedure are available in the called procedure.

    Try it!

    eg:

    procedure( myProcedureA() let((varA) varA = 123 myProcedureB()))

    procedure( myProcedureB() let((varC varD) println(varA) ))

    myProcedureA()
    123

    println(varA)
    E- *Error* eval: unbound variable - varA
    ERROR

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • skillnewbie
    skillnewbie over 16 years ago

    hi eDave and Anton,

    Thanks for the solution, i tried both of them and it works~

    appreciate your help on this.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • skillnewbie
    skillnewbie over 16 years ago

    hi,

    actually my coding problem is like this:

    I open a form handle in procedureA

    procedure( procedureA()

    let( (list1 list2 myform)

                 list1 = '(a b c d)

                 list = '(e f g h)

                 ...

                  myform = axlFormCreate((gensym) "anyform.form" '("E" "OUTER")   '_ncAction t)

    )

    I want to pass the list1 and list2 (which are defined from procedureA) to the form action procedure "_ncAction" but I want to make them (list1, list2 and myform) local to the 2 procedures only. so I define this in my _ncAction...

    procedure(  _ncAction(ncform list1 list2)               

                   ...

    )

     and an error message is shown "_ncAction: too few arguments (3 expected, 1 given) " . It seems that list1 and list2 are NOT passed to the form action (_ncAction) procedure... is it possible to overcome this?

    Thanks again for help~

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • eDave
    eDave over 16 years ago

    Try this method:

    myform = axlFormCreate((gensym) "anyform.form" '("E" "OUTER")   '_ncAction t)

    myform ->list1 = '(a b c d)

    myform ->list = '(e f g h)

    in your callback funtion you can retrieve the lists by using:

    ncform ->list1 and ncform ->list

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
>
Cadence Guidelines

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