Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Compatibility issues with cmd.exe

May
1
0
Hi,

Here is a list of compatibility issues with cmd.exe that I'm facing.
This is on Windows 7, locale is 40c (French/France).


echo %TIME%
cmd.exe: 3:52:08,99
tcc.exe: 03:52:08.99
- decimal separator
- padding
time /T
cmd.exe: 03:52
tcc.exe: 03:52:08
- seconds
ver
cmd.exe: Microsoft Windows [version 6.1.7601]
tcc.exe: TCC LE 12,10,65 Windows 7 [Version 6,1,7601]
- decimal separator should not be used there
Labels
Exemple: http://cpansearch.perl.org/src/DOLMEN/Win32-App-which-1.01/bin/which.cmd
cmd.exe: ok
tcc.exe: fails to go to VisitPATH

dolmen.
 
Hi,
Here is a list of compatibility issues with cmd.exe that I'm facing.
This is on Windows 7, locale is 40c (French/France).

echo %TIME%
cmd.exe: 3:52:08,99
tcc.exe: 03:52:08.99
- decimal separator
- padding
time /T
cmd.exe: 03:52
tcc.exe: 03:52:08
- seconds
ver
cmd.exe: Microsoft Windows [version 6.1.7601]
tcc.exe: TCC LE 12,10,65 Windows 7 [Version 6,1,7601]
- decimal separator should not be used there

All WAD (and Take Command/TCC have behaved that way for 15 years). Those are all either features or expected behavior, and changing them would likely cause problems for Take Command users.

Why are these problems?

Labels
Exemple: http://cpansearch.perl.org/src/DOLMEN/Win32-App-which-1.01/bin/which.cmd
cmd.exe: ok
tcc.exe: fails to go to VisitPATH

Why do you think:

: == VisitPATH ==

is valid syntax? Granted, CMD is ignoring the ='s, but why would you put them there in the first place? (I've never seen this CMD behavior documented anywhere, and this is the first time in 20 years I've seen somebody trying to do this!)
 

Similar threads

Back
Top