bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: missing man example


From: Aharon Robbins
Subject: Re: missing man example
Date: Tue, 2 Jul 2002 11:31:02 +0300

> Date: Sun, 30 Jun 2002 14:29:57 +0000 (UTC)
> From: root <address@hidden>
> To: Aharon Robbins <address@hidden>
> Cc: address@hidden
> Subject: Re: missing man example
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> > > ls | awk '{print |"echo for each line pass " $0 "to echo"} '
> > First, this has a bug in it.  The pipeline should be
> > closed, otherwise it's possible to run out of processes:
> >     ls | awk '{ print |"echo for each line pass " $0 "to echo"
> >                 close("echo for each line pass " $0 "to echo") }'
> > Second, it is probably better to do it this way:
> >     ls | awk '{ system("echo for each line pass " $0 "to echo") }'
> > Third, it's not clear to me why the lack of this example
> > is a problem.  Can you justify what is so special about it
> > that it absolutely has to be included on the man page?
>
> it is _very_ usefull. as you see i did it wrong even with help of few
> people:/
> maybe URL to awk tutor online would be sufficient ? i really lack in this
> for perl, awk and other languages...
>
> thanks for help !

The online version of the gawk manual may be found at

        http://www.gnu.org/manual/gawk/

I still don't see why passing data to echo is more useful
than something like

        ls | awk '{ print "something about", $0, "here" }'

Arnold



reply via email to

[Prev in Thread] Current Thread [Next in Thread]