Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ucsd!ucbvax!agate!astroplasma.berkeley.edu!richmond
From: richmond@astroplasma.berkeley.edu (Michael Richmond)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Bugs in /bin/csh in AIX version 2.2.1
Message-ID: <1991Jan31.192649.6510@agate.berkeley.edu>
Date: 31 Jan 91 19:26:49 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: richmond@astroplasma.berkeley.edu (Michael Richmond)
Organization: Dept of Astronomy, UC Berkeley
Lines: 32


  We have run into a number of bugs with /bin/csh on our RTs after upgrading
them to AIX version 2.2.1.  Specifically, the csh variable expressions 
$< and $#argv give us trouble, as these transcripts show:

       % set a=$<
       Missing name for redirect.
       % cat > foo
       #!/bin/csh
       echo $#argv
       ^D
       % chmod +x foo
       % foo
       Variable syntax.
       %

  I have suspicions about other csh expressions failing, also.  We have the
version 2.2.1 manuals for AIX, and they say that these csh expressions 
SHOULD work.

  Can anyone tell me if, indeed, the 2.2.1 /bin/csh is royally screwed up?
Here's the 'ls' output for our /bin/csh, in case it helps to identify it:

    % ls -l /bin/csh
     204 -r-xr-xr-x  1 bin      bin        100820 Mar 29 1990  /bin/csh

Is there some documentation for the new 'features?'  Can we be safe by
switching our programming to the Bourne shell?  Thanks for any help
you can give me.

--                                          Michael Richmond
"This is the heart that broke my finger."   richmond@bait.berkeley.edu