Validations of Variable usage
Posted: Tue Feb 01, 2011 4:24 am
This is not a problem, merely a suggestion.
I've just spent half a hour finding out why a file didn't copy (using Run Program 'cmd.exe /c copy "$THIS" "$THAT$"').
I'm using this because the Copy/Move Files won't allow (unfortunally) for variables.
It didn't copy because (and you might've spotted it already) the THIS variable didn't close with the dollar sign.
It works now, but I just (let's call it a feature request
) wondered if the parser of the script code shouldn't have caught that.
Think along the lines of a nice messagebox that says something like 'Closing $ sign not found, is this intentional ?'
Cheers
I've just spent half a hour finding out why a file didn't copy (using Run Program 'cmd.exe /c copy "$THIS" "$THAT$"').
I'm using this because the Copy/Move Files won't allow (unfortunally) for variables.
It didn't copy because (and you might've spotted it already) the THIS variable didn't close with the dollar sign.
It works now, but I just (let's call it a feature request
Think along the lines of a nice messagebox that says something like 'Closing $ sign not found, is this intentional ?'
Cheers