Herbert Xu wrote:
>Hi:
> Up till now there has been no policy on whether one should use
>#!/bin/sh -e or do set -e in a script. I think we should gradually deprecat
>e
>the latter in favour of #!/bin/sh -e because with it one can override the -e
>option by doing something like "/bin/sh script". This would help in debuggi
>ng
>faulty scripts or forcing a script to ignore errors in weird circumstances.
>Would anyone object to this if this were done say for slink?
There are cases where one wants to sandwich a section of code with `set -e'
`set +e'. Policy should not be so rigid as to exclude the possibility
of doing this.
--
Oliver Elphick [EMAIL PROTECTED]
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"In my Father's house are many mansions: if it were not
so, I would have told you. I go to prepare a place for
you. And if I go and prepare a place for you, I will
come again, and receive you unto myself; that where I
am, there ye may be also." John 14:2,3
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
