Allow subsequences to pass parameters to callers by value (instead of only by reference)

[RyanWright]

Currently, the only way to pass parameters from a subsequence to a caller is by reference.  It would be nice if you could also pass parameters to callers by value to prevent the callers from modifying them.

[GarryG]

This is a great idea, Ryan.  I was very much looking for the same functionality.  I think having to protect the variable with a lock or semaphore is onerous.

[Arlyn]

Good point Ryan, I hope that gets implemented.

[Al.B]

Hi Ryan,

You can currently configure how a parameter is passed through the right-click menu for the parameter.  

If you deselect "Pass By Reference", changes to the parameter in the subsequence will not modify the property you passed in from the calling sequence.  Is this the behavior you are looking for?

[~jiggawax~]

There is no point in preserving the memory of a callee once it has completed execution.  As far as I understand the memory space is gone once it returns.

Because you need to store that value somewhere in the caller then why not just use the Pass By Reference and give it your variable.

Maybe I'm missing something?

[Elaine_R.]

This feature already exists? you have to set it inside the subsequence when you define the parameters, I thought. same as strict vs. flexible type checking...