BLOCK_INPUT in compile_pattern_1

[Stefan Monnier]

Richard, concerning your question:

  /* Doing BLOCK_INPUT here has the effect that
     the debugger won't run if an error occurs.
     Why is BLOCK_INPUT needed here?  */

I don't have a firm answer, but I suspect that it may have been due to the
fact that re_compile_pattern may call `malloc'.  And since our
signal-handling routines can also call `malloc' (unless we use SYNC_INPUT),
we have to be careful to BLOCK_INPUT around any direct or indirect call
to malloc.


        Stefan