This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [wwwdocs] Porting to again


On Wed, 18 Feb 2015, Marek Polacek wrote:
> This is a revised version.  I reworded the paragraph dealing with
> __STDC_VERSION__, made some clarifications wrt %a, and added some
> text wrt cpp -P issue.

I made some minor changes on top of this:
- Use a shorter URL for a PR reference.
- Avoid a "here" link.
- Various wording changes.

With that I am nearly through for everything related to the GCC 5.1
release. ;-)

Gerald

Index: porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/porting_to.html,v
retrieving revision 1.8
diff -u -r1.8 porting_to.html
--- porting_to.html	18 Apr 2015 19:45:17 -0000	1.8
+++ porting_to.html	20 Apr 2015 00:22:50 -0000
@@ -29,19 +29,20 @@
 
 <p>The preprocessor started to emit line markers to properly distinguish
 whether a macro token comes from a system header, or from a normal header
-(see <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60723";>PR60723</a>).
-These new markers can cause intriguing problems, if the packages aren't ready
+(see <a href="https://gcc.gnu.org/PR60723";>PR60723</a>).
+These new markers can cause intriguing problems for software not ready 
 to handle them.  To stop the preprocessor from generating the <code>#line</code>
-directives, use the <code>-P</code> option, documented
-<a href="https://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html#Preprocessor-Options";>here</a>.
-Consider the following snippet:</p>
+directives, use
+<a href="https://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html#Preprocessor-Options";>the <code>-P</code> option</a>.</p>
+
+<p>Consider the following snippet:</p>
 
 <pre><code>
   #include &lt;stdlib.h&gt;
   exitfailure EXIT_FAILURE
 </code></pre>
 
-While older "gcc -E" used to emit:
+In the past "<code>gcc -E</code>" used to emit:
 
 <pre><code>
 # 2 "t.c" 2
@@ -57,7 +58,7 @@
            1
 </code></pre>
 
-As can be seen, the <code>exitfailure</code> and <code>1</code> tokens
+Observe how the <code>exitfailure</code> and <code>1</code> tokens
 are not on the same line anymore.
 
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]