From owner-freebsd-arch Tue Apr 11 15:24:48 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 39E0A37BB38 for ; Tue, 11 Apr 2000 15:24:39 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id AAA19924 for ; Wed, 12 Apr 2000 00:24:40 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA00634 for freebsd-arch@freebsd.org; Wed, 12 Apr 2000 00:24:35 +0200 (CEST) Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 7F7FB37BB13 for ; Tue, 11 Apr 2000 15:24:27 -0700 (PDT) (envelope-from jeremyp@pc0640.alcatel.com.au) Received: by border.alcanet.com.au id <115234>; Wed, 12 Apr 2000 08:24:46 +1000 From: Peter Jeremy Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh In-reply-to: <200004110008.RAA29263@usr09.primenet.com>; from tlambert@primenet.com on Tue, Apr 11, 2000 at 10:09:30AM +1000 To: Terry Lambert Cc: arch@freebsd.org Message-Id: <00Apr12.082446est.115234@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200004110008.RAA29263@usr09.primenet.com> Date: Wed, 12 Apr 2000 08:24:42 +1000 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 11, 2000 at 10:09:30AM +1000, Terry Lambert wrote: >The problem is not that "csh" scripts from other systems won't run >on "tcsh", the problem is that if someone naievely writes code >thinking that the result will then run on some other box, when in >fact it will not, because that boxes "csh" has not be replaced >with "tcsh". Leaving aside the issue of the sanity of anyone who writes csh scripts... Exactly the same arguments could be made about our C compiler (which supports a number of extensions to ANSI C), our awk (which supports extensions to the language defined in the AWK book), our troff (which includes extensions to ditroff), our tar, our dd, and presumably many others. The obvious solution is to have a 'csh-compatibility' mode (I don't know if tcsh has one or not). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message