From owner-freebsd-arch Tue Apr 11 15:59: 9 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 B412937BA31 for ; Tue, 11 Apr 2000 15:58:59 -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 AAA20374 for ; Wed, 12 Apr 2000 00:59:03 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA00769 for freebsd-arch@freebsd.org; Wed, 12 Apr 2000 00:58:58 +0200 (CEST) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id D5BF537B8FF for ; Tue, 11 Apr 2000 15:58:40 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id PAA21380; Tue, 11 Apr 2000 15:58:30 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpdAAATeaaJP; Tue Apr 11 15:58:16 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA09930; Tue, 11 Apr 2000 15:58:19 -0700 (MST) From: Terry Lambert Message-Id: <200004112258.PAA09930@usr09.primenet.com> Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh To: peter.jeremy@alcatel.com.au (Peter Jeremy) Date: Tue, 11 Apr 2000 22:58:19 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), arch@freebsd.org In-Reply-To: <00Apr12.082446est.115234@border.alcanet.com.au> from "Peter Jeremy" at Apr 12, 2000 08:24:42 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >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. By golly, you're right! 8-). I've made the argument many times that the compier should be an add-in, and one of the options should be TenDRA (or the OSF compiler, on the Alpha), and that we should seperate all assembly code from C code so that we could have C versions of everything, and greatly facilitate porting -- as well as assembly versions being written by the people who own the platforms. I've recently had problems with man pages on another system using real "troff" because of the macro extensions. > The obvious solution is to have a 'csh-compatibility' mode (I don't > know if tcsh has one or not). Actually, a "kernel.turn_off_all_the_platform_specific_extensions=1" is something else I've wanted for BSD's, to let a developer write code that will run on all BSD systems. I think the first BSD platform to get this option will win, in fact, because all commercial developement would immediately move there to target all BSD platforms, instead of one at a time. Don't tell the Linux folks, though... if they steal the idea, then we are doomed... ;^p Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message