[asterisk-dev] policy change for correct handling of fatal program conditions

[Tilghman Lesher]

On Wednesday 24 January 2007 16:00, SF Markus Elfring wrote:
> > Well, if not, then all calls fail in their own due time.  This is
> > still the "right thing" to do, and you have not made an argument
> > for why the process would do better to call exit().
>
> The function "set_var" shows a simple example. It tries to add a
> variable to a global list in a thread-unsafe way. How important is
> this operation for correct program behaviour?
> http://svn.digium.com/view/asterisk/trunk/utils/check_expr.c?rev=4723
>2&view=markup

This is a single threaded utility program.  Given that there are no
other threads executing, "thread-unsafe" is completely irrelevant.

-- 
Tilghman