Not in functions that expect a file name (but I didn't do an exhaustive search). As expected, generic string functions (like @LEN) treat the quotes as significant.
That's a very good argument for not having DO arguments automatically quoted.
For example;
Code:
v22.00.31_$*echo %_cmdspec
D:\TCMD v22\TCC.EXE
v22.00.31_$do var in "%_cmdspec" (echo %var & echo %@len[%var])
D:\TCMD v22\tcc.exe
19
v22.00.31_$do var in /L %_cmdspec (echo %var & echo %@len[%var])
D:\TCMD
7
v22\TCC.EXE
11
v22.00.31_$do var in /t"" /L %_cmdspec (echo %var & echo %@len[%var])
D:\TCMD v22\TCC.EXE
19
Not an extensive example, but it does illustrate the point. I have scripts and aliases that use other variable functions, some needing quotes and some not. Just have to be careful of the intended use and quote where required for a correct result.
Perhaps someone would like to invest the time to write an exhaustive btm to test all the permutations. Considering the extensive number of variables and functions in TCC this could be a very time consuming exercise or not.
