I have to call .cmd scripts from TCC wich contain environment variables with embedded dots like:
set A.B.C=something
and later use them in this way:
echo %A.B.C%
I will not get
something
(thats what CMD.EXE yields) but
.B.C
because TCC treats the first dor as terminator and, of course %A is not defined.
Would it be possible to:
1) add a switch to setdos that allows dots in variable names?
2) allow dots in *.cmd scripts all the time?
or is there already a work-arround.
Thanks for your suggestions
set A.B.C=something
and later use them in this way:
echo %A.B.C%
I will not get
something
(thats what CMD.EXE yields) but
.B.C
because TCC treats the first dor as terminator and, of course %A is not defined.
Would it be possible to:
1) add a switch to setdos that allows dots in variable names?
2) allow dots in *.cmd scripts all the time?
or is there already a work-arround.
Thanks for your suggestions