USER_GET_MESHDATA, RETURN, RELEASE
 

Hello! Can you tell me, I should use RETURN, RELEASE CALLS for every function... Or enough do it for block of functions?

Re: USER_GET_MESHDATA, RETURN, RELEASE
 

Dear Vladimir,

If the documentation indicates that RELEASE is available, you should RELEASE the variable once you are done with it.

Opaque

Re: USER_GET_MESHDATA, RETURN, RELEASE
 

I should to do:

1)

USER_GET_MESHDATA(....,'RETURN',....) ........ USER_GET_MESHDATA(....,'RETURN',....) USER_GET_MESHDATA(....,'RETURN',....) USER_GET_MESHDATA(....,'RETURN',....) ..... USER_GET_MESHDATA(....,'RELEASE',....)

or

2) USER_GET_MESHDATA(....,'RETURN',....) USER_GET_MESHDATA(....,'RELEASE',....)

USER_GET_MESHDATA(....,'RETURN',....) USER_GET_MESHDATA(....,'RELEASE',....)

USER_GET_MESHDATA(....,'RETURN',....) USER_GET_MESHDATA(....,'RELEASE',....)

USER_GET_MESHDATA(....,'RETURN',....) USER_GET_MESHDATA(....,'RELEASE',....)

Re: USER_GET_MESHDATA, RETURN, RELEASE
 

Dear Vladimir,

My style is "first in-last out" or "last in, first out". That is,

USER_GET_MESHDATA(....'OPTION 1','RETURN',....)

USER_GET_MESHDATA(....'OPTION 2','RETURN',....)

USER_GET_MESHDATA(....'OPTION 3','RETURN',....)

Compute what you need, and after you are done.

USER_GET_MESHDATA(....'OPTION 3','RELEASE',....)

USER_GET_MESHDATA(....'OPTION 2','RELEASE',....)

USER_GET_MESHDATA(....'OPTION 1','RELEASE',....)

Order of the release should not matter as long as you execute them.

Opaque

Re: USER_GET_MESHDATA, RETURN, RELEASE
 

Dear Opaque, Thanks for answer!