Jonathan Larmour wrote: > John Dallaway wrote: >> I was looking at support for UNC file paths in the eCos Configuration >> Tool today. The convoluted #! magic we use in our Tcl scripts to find a >> Cygwin Tcl shell is getting in the way when calling (eg) heapgen.tcl via >> a UNC repository path. This code is only needed to support installations >> of Cygwin that are more than 5 years old. >> >> Rather than increase the complexity of the #! magic still further, I >> think it now makes sense to revert to a simple "#! /usr/bin/tclsh" >> within our Tcl scripts. However, this would break compatibility with old >> Cygwin installations providing only tclsh8*.exe or cygtclsh80.exe. >> >> Any objections? > > Yes, it may not be in /usr/bin. I don't mind the cygwin-specific cygpath > bits being dropped, but I'd still want it to be found from the PATH by some > means.
Does CygWin have '/usr/bin/env'? This is the "modern" way to handle this: #! /usr/bin/env tclsh ... -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
