From owner-freebsd-arch Mon Apr 10 17: 8:56 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 0A38D37B6B4 for ; Mon, 10 Apr 2000 17:08:55 -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 CAA04998 for ; Tue, 11 Apr 2000 02:08:56 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id CAA06444 for freebsd-arch@freebsd.org; Tue, 11 Apr 2000 02:08:53 +0200 (CEST) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 9DB4D37B569; Mon, 10 Apr 2000 17:08:24 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id RAA18992; Mon, 10 Apr 2000 17:07:13 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpdAAAIvaicL; Mon Apr 10 17:07:09 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id RAA29263; Mon, 10 Apr 2000 17:08:15 -0700 (MST) From: Terry Lambert Message-Id: <200004110008.RAA29263@usr09.primenet.com> Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh To: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: Tue, 11 Apr 2000 00:08:15 +0000 (GMT) Cc: obrien@freebsd.org, nate@yogotech.com (Nate Williams), arch@freebsd.org In-Reply-To: from "Satoshi - Ports Wraith - Asami" at Apr 06, 2000 06:28:31 PM 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 > That said, I think it is a good idea to replace csh with tcsh. tcsh > and csh are so close, there is no issue on scripting (I am not aware > of any incompatibilities between tcsh and csh commands that will make > csh scripts fail), 1) Someone writes a "csh" script that uses "tcsh" "enhanced" variable substitution. 2) I then try to run that same script on another system, with a real "csh". 3) The script fails. 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". 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