Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!brl-adm!adm!milgr@brandeis.csnet
From: milgr@brandeis.csnet (Marc Milgram)
Newsgroups: comp.unix.questions
Subject: Re: C shell script files
Message-ID: <11333@brl-adm.ARPA>
Date: 19 Jan 88 22:59:05 GMT
Sender: news@brl-adm.ARPA
Lines: 26

Subject: C shell script files

 Amos Shapir <amos@taux01.uucp> writes:
>Better forget it! Use csh for interactive work, sh (or ksh) for command
>files. The command interface of csh is horrible: you can't nest if's and
>while's,                                         ^^^^^^^^^^^^^^^^^^^^^^^
 ^^^^^^^
Yes you can - though it is kind of ugly
> keywords must be first on their line,
[;^][ \t<label>]*<keyword> ... is the regular expression representing
where keywords can go.  Is this so bad?  Should they be allowed in
other places?

> you can't freely interchange
>semicolons with new-lines, 
You have a point

>you can't pipe the output of while's, etc, etc.
Try enclosing the whiles in ()'s.

I have written shell scripts in both sh and csh.  Currently, I can
write scripts faster in the csh because I use most of the features of
the csh every day, and I almost never use sh.

	-Marc Milgram
	(milgr@brandeis.edu)