Re: possible deadlock on invalid UTF-8 data

On Tue, 2001-11-27 at 14:54, Havoc Pennington wrote:
> On the other hand, the advantage of the endless loop (vs. reading
> invalid memory) is that the bug is immediately evident, and pretty
> easy to track down.

Wouldn't it be even more immediately evident and even easier to track
down if it returned NULL or g_assert-ed or g_error-ed or something.

It seems pathological for a library to signal an error by deadlocking.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]