Re: abort() calls

Folker Schamel wrote:
> Stefan Küng wrote:
>> If there's any chance that the apr pools can clean up something, then
>> the subversion lib should return an error and not call abort() at all.
>> Because that's a situation which I would consider as manageable, and
>> such situations should never call abort(). IMHO, abort() should only be
>> used as the absolutely last resort, if really there's absolutely *no*
>> other way to recover.
>
> What situation could that be?

The only situation I can think of is out-of-memory. Then it's not
possible to create an error anymore (that needs memory for the error
string).
But there may be more situations. It's just that while looking through
the code where abort() is currently used, there's every time a good
chance to recover and return an error.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org