From owner-freebsd-current  Wed Mar 14  6:10:14 2001
Delivered-To: freebsd-current@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id 5900737B71C
	for <current@FreeBSD.ORG>; Wed, 14 Mar 2001 06:10:07 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from salmon.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa44559@salmon>; 14 Mar 2001 14:10:06 +0000 (GMT)
To: "Andrey A. Chernov" <ache@nagual.pp.ru>
Cc: Christos Zoulas <christos@zoulas.com>, tcsh-bugs@mx.gw.com,
	current@FreeBSD.ORG
Subject: Re: tcsh 6.10.00 echo;echo;echo; bug with fix 
In-reply-to: Your message of "Wed, 14 Mar 2001 15:59:08 +0300."
             <20010314155908.A72442@nagual.pp.ru> 
X-Request-Do: 
Date: Wed, 14 Mar 2001 14:10:06 +0000
From: David Malone <dwmalone@maths.tcd.ie>
Message-ID:  <200103141410.aa44559@salmon.maths.tcd.ie>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Since internal 'echo' does nothing, it _not_ used in any old csh scripts,
> while 'echo ""' does the same thing in both old and new variants, so old
> scripts will works in the same way.

Will it change what happens if you do:

	set null=""
	echo $null

(this produces nothing in "traditional" tcsh and csh)?

> Since old csh is not maintained anymore, we don't need to preserve exact
> void compatibility with unsupported and not maintained other platforms
> software with no practical reason.

I guess we should leave it up to the tcsh folks. There are other
internal csh commands which behave differently to external commands
(nice and time come to mind). I think it is known that 'echo ""' is
a relatively portable way of printing a blank line.

	David.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message