1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Compatibility issues with cmd.exe

Discussion in 'Support' started by dolmen, May 7, 2011.

  1. dolmen

    Joined:
    May 6, 2011
    Messages:
    1
    Likes Received:
    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.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,854
    Likes Received:
    83
    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?

    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!)
     

Share This Page