Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2405)

Issue 5558045: [pph] Refuse to generate PPH with #include_next (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 3 months ago by Diego Novillo
Modified:
12 years, 1 month ago
Reviewers:
gcharette1
CC:
Lawrence Crowl, gcc-patches_gcc.gnu.org
Visibility:
Public.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+132 lines, -18 lines) Patch
M gcc/cp/ChangeLog.pph View 1 chunk +20 lines, -0 lines 0 comments Download
M gcc/cp/pph-core.c View 5 chunks +59 lines, -8 lines 0 comments Download
M gcc/cp/pph-in.c View 1 chunk +3 lines, -0 lines 0 comments Download
M gcc/cp/pph-out.c View 2 chunks +22 lines, -2 lines 0 comments Download
M gcc/cp/pph-streamer.h View 2 chunks +2 lines, -0 lines 0 comments Download
M gcc/testsuite/ChangeLog.pph View 1 chunk +4 lines, -0 lines 0 comments Download
A gcc/testsuite/g++.dg/pph/d0include-next.h View 1 chunk +6 lines, -0 lines 0 comments Download
M libcpp/ChangeLog.pph View 1 chunk +6 lines, -0 lines 0 comments Download
M libcpp/files.c View 1 chunk +9 lines, -0 lines 0 comments Download
M libcpp/include/cpplib.h View 1 chunk +1 line, -0 lines 0 comments Download
M libcpp/internal.h View 1 chunk +0 lines, -8 lines 0 comments Download

Messages

Total messages: 3
Diego Novillo
This patch adds a check for #include_next and refuses to generate a PPH image for ...
12 years, 3 months ago (2012-01-18 22:26:52 UTC) #1
gcharette1
Why do you need two functions: pph_stream_close and pph_stream_close_no_flush only to call pph_stream_close_1 with a ...
12 years, 3 months ago (2012-01-28 22:00:24 UTC) #2
Diego Novillo
12 years, 3 months ago (2012-01-29 17:42:49 UTC) #3
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 is simpler...

Well, I find it clearer to have more explicit names for the API than 
using flags.


Diego.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b