Re: Variables not passed out of WHILE
- From: gazelle@xxxxxxxxxxxxxxxxxxxxx (Kenny McCormack)
- Date: Fri, 16 Mar 2007 08:29:35 +0000 (UTC)
In article <7b0pc4-ov1.ln1@xxxxxxxxxxxxxxxxxx>,
Chris F.A. Johnson <cfajohnson@xxxxxxxxx> wrote:
On 2007-03-15, Kenny McCormack wrote:
P.S. This, incidentally, is a good example (and there are many others)
of why using shell as a general purpose programming language (as opposed
to merely using shell as a "host" for a real language like
AWK/perl/whatever) is a bad idea.
On the contrary, it is a good example of why you need to know the
language you are using. The shell is an excellent general-purpose
programming language (but, perhaps, not an all-purpose programming
language).
I fully expected you to say that. But I think it is wrong.
.
- References:
- Variables not passed out of WHILE
- From: Oliver Meister
- Re: Variables not passed out of WHILE
- From: Oliver Meister
- Re: Variables not passed out of WHILE
- From: Kenny McCormack
- Re: Variables not passed out of WHILE
- From: Chris F.A. Johnson
- Variables not passed out of WHILE
- Prev by Date: Re: grep the parameter list is too long.
- Next by Date: Re: vi - Can vi add Characters in the range of line by command?
- Previous by thread: Re: Variables not passed out of WHILE
- Next by thread: how to using getopt in AIX
- Index(es):
Relevant Pages
|