[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Revisiting Error handling (errexit)
From: |
Greg Wooledge |
Subject: |
Re: Revisiting Error handling (errexit) |
Date: |
Mon, 4 Jul 2022 14:45:39 -0400 |
On Mon, Jul 04, 2022 at 09:33:28PM +0300, Yair Lenga wrote:
> Thanks for taking the time to review my post. I do not want to start a
> thread about the problems with ERREXIT. Instead, I'm trying to advocate for
> a minimal solution.
Oh? Then I have excellent news. The minimal solution for dealing with
the insurmountable problems of errexit is: do not use errexit.
It exists only because POSIX mandates it. And POSIX mandates it only
because it has been used historically, and historical script would
break if it were to be removed or changed.
- Revisiting Error handling (errexit), Yair Lenga, 2022/07/04
- Re: Revisiting Error handling (errexit), Saint Michael, 2022/07/04
- Re: Revisiting Error handling (errexit), Lawrence Velázquez, 2022/07/04
- Re: Revisiting Error handling (errexit), Yair Lenga, 2022/07/04
- Re: Revisiting Error handling (errexit),
Greg Wooledge <=
- Re: Revisiting Error handling (errexit), Lawrence Velázquez, 2022/07/04
- Re: Revisiting Error handling (errexit), Yair Lenga, 2022/07/04
- Re: Revisiting Error handling (errexit), Lawrence Velázquez, 2022/07/04
- Re: Revisiting Error handling (errexit), Yair Lenga, 2022/07/05
- Re: Revisiting Error handling (errexit), Lawrence Velázquez, 2022/07/05
- Re: Revisiting Error handling (errexit), David, 2022/07/04
Re: Revisiting Error handling (errexit), Yair Lenga, 2022/07/08