Version 9 of How Tcl differs between Windows and Unix

Updated 2007-01-18 22:09:18 by kpv

Keith Vetter On clt lists: [L1 ]

  • mousewheel handling
  • dash lines
  • rc filename and location
  • where to put temp files
  • $HOME is less prominent in Windows
  • how and for whom you install
  • file permissions
  • file volumes
  • registering as a mime type
  • making script executable (!# & chmod vs. assoc & ftype)
  • font names
  • some windows only color names
  • option database not typically used on windows
  • stdin, stdout and stderr may not work
  • different set of native widgets and dialogs
  • send command
  • some widget padding/border differences but I can't remember what
  • unix numerous windows managers which all behave slightly differently
  • printing

Probably the area that causes the most problems for programmers comes in using exec and coordinating with other programs, such as:

  • launching browsers
  • launching mail agent ("start mailto:..." on windows)
  • most unix apps can be driven via stdin using "open |app w"
  • spaces in file paths much more common on windows
  • many windows commands translate to "cmd /c" or "cmd /c start" which requires eval and careful space handling

LV Hopefully someone will come along and update the above information to discuss the details of the differences. Or, if the differences are large, perhaps turn the outline point into its own series of pages...


See also Cross Platform differences in Tcl/Tk.


Category Porting - Category Windows