Steve, I understand all that. My point is that _my_ scripting (and that of a lot of people on this list) will never, ever, be run on anything other than Linux. Pointing out that portability is a good thing is one thing, claiming that non-portable code is inherently bad is another.
Rick and I see eye to eye on a lot of stuff. I was just pointing out that his "bias" was showing a little, since the scripting work he does, _has_ to run on multiple platforms. Mark Post -----Original Message----- From: Steven A. Adams [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 12:31 AM To: [EMAIL PROTECTED] Subject: Re: .bashrc Hey Mark, I think the point here is that your scripting work has value in OSes other than linux and by conserving the convention of #!/bin/sh you maintain portability. Now by commenting the nature and intent of your script you can warn others of the possible problems with running the code on other shells and accomplish the same results in a more open-source, *nix friendly way. In my opinion, both theories work fine but I can see why some would have a problem with it. Steve On Wed, 2003-03-19 at 21:02, Post, Mark K wrote: > Rick, > > Because most of us don't work for ISV's that support products on UNIX as > well as Linux, and any script we write will only be running on Linux? I > frequently code my scripts that way because I want them to be treated as > bash scripts and not sh scripts. > > Mark -- Steven A. Adams <[EMAIL PROTECTED]>
