Xref: utzoo comp.unix.questions:32060 comp.unix.shell:2368
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uunet!mcsun!unido!sbsvax!mg
From: mg@sbsvax.cs.uni-sb.de (Michael Greim)
Newsgroups: comp.unix.questions,comp.unix.shell
Subject: Re: Is my shell broken or what?
Summary: It's a bug, not a feature
Message-ID: <11375@sbsvax.cs.uni-sb.de>
Date: 10 Jun 91 16:11:16 GMT
References: <1991Jun7.045124.26811@ux1.cso.uiuc.edu>
Followup-To: comp.unix.questions
Organization: Universitaet des Saarlandes, Saarbruecken, Germany
Lines: 25

In article <1991Jun7.045124.26811@ux1.cso.uiuc.edu>, phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN) writes:
> Here is the session example:
> 
[...]
> phil@ux1:/cso/staff/phil 4> echo ${test2}
> Variable syntax.
[...]
> 
> I have seen before where things like csh have little bugs here or there
> that are different from vendor to vendor.  Are the vendors getting into
> the code and changing stuff?

It's a well known bug in csh.
If you play around a little you will notice that the handling of
names differs in "foreach", $-expansion, "set" ... constructs.
I have fixed it some years ago, and if you are lucky enough to have source,
you can apply the patches available at our ftp-server cs.uni-sb.de
(134.96.252.31) in /pub/bsd/csh.

	-mg
-- 
 .-. .-.  .-.  Michael Greim
(   X   )( __) e-mail : mg@cs.uni-sb.de
 \ / \ /  \ /  or     : ...!uunet!unido!sbsvax!mg
  ~   ~    ~