SI-7295 Fix windows batch file with args containing parentheses #3065
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In command scripts, substitution of
FOO
inif cond ( %FOO% )
happensbefore the condition is evaluated. One can use delayed expansion with
if cond (!FOO!)
to get a saner behaviour. Or, as I ended up doing here, usea goto in the body of the if rather than referring directly to variables
there.
Here's a cut down version to demonstrate the old problem:
I don't understand exactly why the parentheses only mess things up in this
situation. But regardless, lets find another way.
My first attempt to fix this was based on the suggestion in the ticket. But,
as shown below, this fails to capture the -toolcp.
Last stop was the goto you'll find in this patch.
With this patch applied, I tested on Windows 8 with the following: