Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 21241
  • 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

Returning value from a function

netbug

Dear all,

I have written the function below, which only checks if a given file exists or not, and I would like it to return the value stored into retValue.

As far as I know, SKILL returns the value of the last line of code (is this correct ?).

If I write the code as below, I will get the error:

*** Error in routine eval:
Message: *Error* eval: unbound variable - retValue

However, if I replace retValue by retValue=isFileName(myFilePath) it will work,but, from my point of view, this is an example of ugly code, since I am evaluating the function twice. Is there another way to do this ?

If the variable retValue retains always the correct value, why does it get unbound after the if instruction end ?

Thanks in advance,

José

procedure(fileExists(myFilePath)
                   let((retValue)
                   retValue=isFileName(myFilePath) ; Test if the file exists

                   ; Check if config file exists
                   if((retValue==t) then
                          printf("fileExists: File Exists !")
                   else
                         printf("fileExists: File does not Exist !")
                   ); end if
                   ); End letmypath
                   retValue                              ; Return Value
); End procedure

Parents

  • Hi José,

    A simpler solution would be to specify the callback for the form as a list of two callbacks. Usually you specify a single string (say), but if you look in the documentation you can specify the OK and Cancel action by specifying a list. Then you can have different callbacks for OK/Apply and Cancel. This is definitely simpler than adding back custom buttons each with a callback.

    For your second question, generally speaking you shouldn't expect the form to return something. It's better practice to use the form callback to do the next phase of your operations. Why is that? Well, if you have an Apply button on the form, the call to hiDisplayForm() won't return - it only returns when you hit OK or Cancel (unless you have set ?dontBlock t when creating the form, in which case it returns immediately). So it's considered bad form (excuse the pun) to rely on the return value from hiDisplayForm().

    For your third question, you can customise the help behaviour. It's not that straightforward, but it is covered in the documentation...

    Regards,

    Andrew.

Reply

  • Hi José,

    A simpler solution would be to specify the callback for the form as a list of two callbacks. Usually you specify a single string (say), but if you look in the documentation you can specify the OK and Cancel action by specifying a list. Then you can have different callbacks for OK/Apply and Cancel. This is definitely simpler than adding back custom buttons each with a callback.

    For your second question, generally speaking you shouldn't expect the form to return something. It's better practice to use the form callback to do the next phase of your operations. Why is that? Well, if you have an Apply button on the form, the call to hiDisplayForm() won't return - it only returns when you hit OK or Cancel (unless you have set ?dontBlock t when creating the form, in which case it returns immediately). So it's considered bad form (excuse the pun) to rely on the return value from hiDisplayForm().

    For your third question, you can customise the help behaviour. It's not that straightforward, but it is covered in the documentation...

    Regards,

    Andrew.

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.