[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: newline cache
From: |
Eli Zaretskii |
Subject: |
Re: newline cache |
Date: |
Tue, 22 Apr 2014 20:46:16 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: Eli Zaretskii <address@hidden>, address@hidden
> Date: Tue, 22 Apr 2014 10:28:19 -0400
>
> Maybe add a monitoring code, which (when enabled at compile-time) always
> checks the return value of that cache against the non-cached result?
As I explained in a previous message, when the value returned by the
cache is wrong, it's too late, because the corruption happened some
time in the past. It's like debugging memory allocation bugs by
catching exceptions in 'free'.
- newline cache, Richard Stallman, 2014/04/21
- Re: newline cache, Eli Zaretskii, 2014/04/21
- Re: newline cache, Richard Stallman, 2014/04/23
- Re: newline cache, Eli Zaretskii, 2014/04/23
- Re: newline cache, Richard Stallman, 2014/04/23
- Re: newline cache, Eli Zaretskii, 2014/04/25
- Re: newline cache, Eli Zaretskii, 2014/04/26
- Re: newline cache, Eli Zaretskii, 2014/04/26
- Re: newline cache, Jarek Czekalski, 2014/04/29