> Unix and POSIX programming environments don't promise the kind of > "write-once-run-anywhere" property that Java does (or did). Look > around and > you'll see lots of scripts that use "uname" to condition details of their > operation, when necessary. In the case of "features" like non-standard > operator synonyms, I think it's best simply to avoid them. Personally, I > have a pretty fast system, and I often just use "/bin/bash" explicitly in > the #! lines, but even that is risky, since that executable isn't > guaranteed to exist (the whole #! thing, lacking PATH searching, is a > portability problem).
perhaps a little offtopic, but you can use /usr/bin/env <program name> to search for a program using the current path, e.g.: #!/usr/bin/env perl means you don't need to know where perl is installed. Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
