anchor.diff:  
   :# Locate and start the Tcl interpreter
   :Start
  -set TCLSH=""
  -for /f "delims=" %%p in ('%ARG0% %VERBOSE% -f') do set TCLSH="%%p"
  -:# Note: The set command above fails without the quotes around %%p. Why?!?
  -:#       (Is it linked to the parenthesis in the "C:\Program Files (x64)" path?)
  -if .%TCLSH%.==."". (
  -  echo>&2 Failure. No tclsh interpreter found.
  +set "TCLSH="
  +call :FindTclsh TCLSH
  +if not defined TCLSH (
  +  >&2 echo Failed. No tclsh interpreter found.
     exit /b 1
   )
   :# Start it
  -%TCLSH% %*
  -goto :eof
  +"%TCLSH%" %*
  +exit /b
   :# End of the PowerShell comment section protecting the batch section.
   #>
   
  
positive.code: echo Options:
  echo   -?        Display this help
  echo   -f        Find the latest tclsh*.exe, and display its pathname
  echo   -s        Setup Windows for running .tcl scripts with the latest tclsh
  echo   -t        Test the current setup. Tells if it's useful to use -s.
  goto :EOF
  
  :Main
  
negative.code: if .%1.==./?. goto Help
  if %1==--call goto Call
  if %1==-d set "DEBUG=1" & goto nextarg
  if %1==-f call :FindTclsh & exit /b
  if %1==-t echo Please use TclSetup.bat instead & exit /b 1
  if %1==-s echo Please use TclSetup.bat instead & exit /b 1
  if %1==-v set "VERBOSE=-v" & goto nextarg
  if %1==-V (echo %VERSION%) & goto :eof
  if %1==-X set "NOEXEC=1" & goto nextarg
  goto start
  
  :# Mechanism for calling a subroutine from the command line
  :Call
  