Quoted "strings" in batch files

[Michael Bulgrien]

Here's a nit. With the batch/command file format, string values cannot wrap around to a new line.

In other words, even if you treat single and double-quotes as quoted values for a batch file (which is helpful for comparisons even if not 100% correct syntax) they should terminate at the end of the line even if there is no closing quote.

http://screencast.com/t/LqPfhKCuz

P.S. The root cause of the screen shot above is that single quotes were accidentally put at the beginnings of lines instead of :: to comment them out. So really is a user error. But if it is no big deal to terminate quotes at the end of a line, I would appreciate the change. No biggie if you don't agree and decide not to do it.

[Michael Bulgrien]

The purpose of the above screen shot was to show that lines with no changes are showing up in difference blocks. In fact, the only differences between the left and right pane are the leading single quotes in front of some of the lines. Since batch statements cannot span multiple lines, this should not occur. Note also that single and double quotes terminate each other. Please ensure that double quotes are only terminated by another double quote or an end-of-line marker. Also, please ensure that single quotes are only terminated by single quotes or an end of line marker.

[Chris]

Michael,

Thanks for pointing this out. I'll update the batch file format for our next release of Cirrus.