Date: Thu, 11 Nov 2004 14:04:09 -0800 (PST) From: ctodd@chrismiller.com To: Kevin Lyons <klyons@corserv.corserv.com> Cc: freebsd-hackers@freebsd.org Subject: Re: tcsh is not csh Message-ID: <Pine.BSI.4.58L.0411111348541.13708@vp4.netgate.net> In-Reply-To: <200411112237.iABMb6YV001471@corserv.corserv.com> References: <200411112237.iABMb6YV001471@corserv.corserv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Nov 2004, Kevin Lyons wrote: > I have (re)discovered that tcsh is not csh although the tcsh man page > falsely asserts backward compatibility. Trying to do a simple read of > multiword variables in tcsh fails yet works find on csh. The tcsh man page > admits as much when one gets to the $< part. > > The point is, csh should be the basic backward compatibly lowest common > denominator between systems. This is a real problem. I humbly suggest that > those that want the bang of tcsh can do a pkg_add just like the morons that > want bash instead of sh. > > If you want to try an example, do the following on csh, and then on tcsh. > #!/bin/csh > echo enter some words > set line = $< > set words = ($line) > echo line is $line > echo word1 is $word[1] > echo word2 is $word[2] > echo word3 is $word[3] > > ------ > The fact that tcsh can not do this in default mode is beyond pathetic. What > is worse is that freebsd didn't notice or care. > . Normally I'd just keep my mouth shut, but... From what you've detailed, you bring up some valid points about tcsh/csh intercompatibility. I'm not sure why this is the case, but like most things a compromise is necessary from time to time and I'm sure there was a good reason. Maybe it was just an oversight when tcsh was ported to FreeBSD and it's just a low priority fire or it's not even a known problem until today. What I choose to take issue with is your assumption that this is the direct and calculated result of the actions of the FreeBSD team, and more over the arrogant nature of your post. As far as I am aware (but since I'm not going to spend any time researching this, I could be wrong), tcsh's origins are not from the FreeBSD project. If there's a FreeBSD specific implementation problem, then it should be logged as a bug, or a "why does tcsh do this?" should be posted to the appropriate list. Sending a "this is beyond pathetic" message to the hackers list is just in bad form and frankly immature. This is a place to get help from people that donate their valuable time. If you want to criticize someone, I would suggest Redmond as a starting point. I'll take this opportunity to thank all those that contribute to this list. Without your help I personally would not have been able to get past some problems I've had over the years, and with your help I've been able to do some really cool things with my BSD systems. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.58L.0411111348541.13708>