Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!yale!cmcl2!philabs!sunrise!ursa!sdo
From: sdo@ursa.UUCP
Newsgroups: comp.unix.wizards
Subject: Sun and 4.3 csh (was lpd problems)
Message-ID: <185@teddy.ursa.UUCP>
Date: Thu, 26-Mar-87 12:37:05 EST
Article-I.D.: teddy.185
Posted: Thu Mar 26 12:37:05 1987
Date-Received: Sat, 28-Mar-87 06:48:29 EST
References: <5483@brl-adm.ARPA> <4914@garnet.Diamond.BBN.COM>
Reply-To: sdo@teddy.UUCP (Scott Oaks)
Organization: Bear Stearns, New York
Lines: 26

>>                            If SUN passed on a Berkeley bug it becomes
>>SUN's bug, because they were the last to muck with it.
>
>Except that it's NOT A BUG.  It's a FEATURE.  It's SUPPOSED to work that
>way.  Since Sun 3.2 csh claims to be compatible with 4.3 csh, it would 
>have been a bug NOT to change the behavior.  SunOS certainly has its share 
>of bugs, but let's be fair about finger pointing.

Granted that the upgrade was necessary (and important, since it allows
other arguments to be passed on the command line), I think the real point
here not whether the change ought to have been made (it ought) but what
Sun should have done about the fact that it was made.

The only way to find out about the change was to do a man csh after the
upgrade.  This is a little unreasonable -- obviously no one is going to 
read 8 sections of UNIX manuals to find out if things are upward compatable.
If Sun had made a section in the release notes about programs which are not
iupward compataible, everyone would have made the change initially, and this
discussion would have been avoided.  Instead, a lot of things failed for
a lot of people who had to put in a lot of extra hours to track down what
is essentially a minor change.
-- 
Scott Oaks
Bear Stearns
(212) 952-3164
{convex, sunrise, cuctr}!ursa!sdo