Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!feeder.news-service.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: John Stumbles Newsgroups: comp.os.linux.misc Subject: Re: calling script function on output of find Date: 10 Jul 2011 23:14:14 GMT Lines: 18 Message-ID: <97uq26Fr24U1@mid.individual.net> References: <97g5odFp36U1@mid.individual.net> <97o2suFrvqU1@mid.individual.net> <97r16hFb0uU4@mid.individual.net> <0v8oe8xcrt.ln2@news.roaima.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net 6F+n+frQX9YSP81UhjDjfAvlv0TbYUNXwdXKORv9dftdjkPotd Cancel-Lock: sha1:tWyhpVO+liF8vKuuH07a+siAZz4= User-Agent: Pan/0.133 (House of Butterflies) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:1738 On Sun, 10 Jul 2011 10:45:36 +0100, Chris Davies wrote: > But yes, perl (or ruby, or python, or any other decent programming > language) could be an alternative. The trade off is convenience vs > perfection vs speed of solution. If I'm writing a one-liner I tend to > write quick and dirty. As soon as I realise it's got more general > possibilities I expand it out into a script and (try to) clean up the > rough edges. Or at least ensure it fails cleanly on just cases. I stopped doing things like this in Perl a few years back and forced myself to learn to do them in shell, just for the educational variety. Now I'm so rusty I don't know if I *could* do it in Perl :-( -- John Stumbles militant pacifist