On 1/28/12 5:00 PM, Gabriel Charette wrote:
Why do you need two functions: pph_stream_close and
pph_stream_close_no_flush only to call pph_stream_close_1 with a
different flag? Seems like leaving
pph_stream_close_1 as pph_stream_close and simply making the calls
themselves with true/false flags
This patch adds a check for #include_next and refuses to generate a
PPH image for files that use it.
Since the discovery of #include_next comes well into the
pre-processing stage (after we've initialized PPH data), we need to
undo what we did and disable PPH. To do that, there is a new function
