Re: sed

[Stephane Chazelas]

On Tue, Feb 13, 2007 at 03:14:59PM -0600, Matthew Woehlke wrote:
[...]
> >The Bourne shell is a legacy shell, just as the Thomson shell
> >was before it. You don't need to make scripts portable to that
> >shell anymore unless you want to support 15 year old systems,
> 
> Funny, I wasn't aware that Solaris 10 is "15 years old" already. (Though 
> why Sun is keeping good old broken Bourne alive is beyond me.)

Solaris's sh has been POSIX (except for various bugs) for a long
time. I'm pretty sure it was already in Solaris 5.

You may be looking at the wrong sh. Solaris's sh is in
/usr/xpg4/bin. The one in /bin or /usr/bin is a legacy one for
backward compatibility. "getconf PATH" on Solaris does return
/usr/xpg4/bin before /usr/bin.

What is a pitty is that the $PATH is not the default in most
Solaris deployments.

A shortcoming of POSIX/SUS is that they don't define a standard
way to put yourself into a conformant environments (for
instance, the #! is non-standard).

> At any rate, I'll concede your point on "standard" vs "portable". 
> However, some of us don't have the luxury of 100% POSIX compliant 
> environments. (I still have to deal with nsr-tandem-nsk!)

Sure, but the best way to move things forward is to use the
standard syntax in one's scripts.

-- 
Stéphane