Glenn Fowler writes: > I was thinking "user shell script application" and should have typed it > once a script strays from PATH=$(getconf PATH) it may come across utilities > on PATH that have parameters different from what getconf tells the script
Yes. You're in essentially undefined (or at least not standards compliant) territory if you have a PATH that doesn't have those special directories listed first on your path. > and that clears it up for me > from a portability+extensions standpoint I almost never stray from plain [g]cc > this has been a good exercise > it also shows that its not worth losing your sanity programming to standard > limits > code for no limits when possible and be blissfully clueless of standard > conundrums I think that's a good policy. The default environment for most OSes should be whatever is sanest on that platform, regardless of what standards may be supported and what they may say. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
