Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!cwns1!chet
From: chet@cwns1.CWRU.EDU (Chet Ramey)
Newsgroups: gnu.bash.bug
Subject: Re: complex functions
Message-ID: <1990Jan23.213142.9163@usenet.ins.cwru.edu>
Date: 23 Jan 90 21:31:42 GMT
References: <11606@thorin.cs.unc.edu>
Distribution: na
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 22

In article <11606@thorin.cs.unc.edu> beckerd@grover.cs.unc.edu (David Becker) writes:

>In particular it doesn't take the typedef flags which isn't too big a
>deal but it also won't swallow ((i=cdlen)).  The double parentheses cause a
>syntax error.

Bash in its current incarnation has neither integer variables (the `typeset
-i' stuff) nor arithmetic expression evaluation (the `((...))' stuff).  It
doesn't have array variables, either.  I don't really know what Brian's
plans for this are, but I did write an expression evaluator and send it to
him.  I have put in integer variables, though not in a way that's really
satisfactory, and I haven't sent that code to Brian.

You could probably hack this stuff to use regular variables and
expr without too much trouble, or use pushd and popd.

Chet
-- 
Chet Ramey				"Can't you pay a grad student to 
Network Services Group			 read the manual for you?"
Case Western Reserve University			-- Bill Wisner,
chet@ins.CWRU.Edu				   	to Peter Honeyman