Re: Ignoring trap command for a grep function
From: Kenny McCormack (gazelle_at_yin.interaccess.com)
Date: 10/25/05
- Next message: Alan Balmer: "Re: Ignoring trap command for a grep function"
- Previous message: Stephen M. Dunn: "Re: cron dies - Cannot create temporary file"
- Next in thread: Alan Balmer: "Re: Ignoring trap command for a grep function"
- Reply: Alan Balmer: "Re: Ignoring trap command for a grep function"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 25 Oct 2005 15:41:10 GMT
In article <Zc2dnZZqfpP6A0jfRVn-2A@comcast.com>,
Henry Townsend <henry.townsend@not.here> wrote:
>Chris F.A. Johnson wrote:
>> On 2005-07-13, sharma.raghvendra@gmail.com wrote:
>>
>>>Hi,
>>>
>>>We have a trap statement for every non zero returning command/function.
>>
>>
>> Don't.
>
>I don't make a habit of disagreeing with CFAJ but must make an exception
>in this case.
Don't be afraid to disagree with CFAJ. His comments, though technically
correct, are rarely useful. It's just like in (the joke newsgroup known,
somewhat comically, as) comp.lang.c. The topic is defined so narrowly and
absurdly that the answers, though technically correct, are useless.
Note, especially, his ridiculous assertion that using "trap ERR" is wrong
because it isn't POSIX and thus, not guaranteed to be present in every
(POSIX) shell. But the OP was already using it (in a large script in an
existing environment, neither of which were going to change)! So, that
complaint is obviously bogus.
- Next message: Alan Balmer: "Re: Ignoring trap command for a grep function"
- Previous message: Stephen M. Dunn: "Re: cron dies - Cannot create temporary file"
- Next in thread: Alan Balmer: "Re: Ignoring trap command for a grep function"
- Reply: Alan Balmer: "Re: Ignoring trap command for a grep function"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
