diff mbox

[fortran,doc] Mention line lengths

Message ID 4D28E915.9030902@netcologne.de
State New
Headers show

Commit Message

Thomas Koenig Jan. 8, 2011, 10:45 p.m. UTC
Hello world,

I think that, after applying this doc patch, we can close PR 46405.
Tested with "make dvi", "make info" and "make pdf".

OK for trunk?

	Thomas

2011-01-08  Thomas Koenig  <tkoenig@gcc.gnu.org>

	PR fortran/46405
	* invoke.texi:  Mention -ffree-line-length-none and
	-ffixed-line-length-none for preprocessing.

Comments

Jerry DeLisle Jan. 8, 2011, 10:55 p.m. UTC | #1
On 01/08/2011 02:45 PM, Thomas Koenig wrote:
> Hello world,
>
> I think that, after applying this doc patch, we can close PR 46405.
> Tested with "make dvi", "make info" and "make pdf".
>
> OK for trunk?
>
> 	Thomas
>
> 2011-01-08  Thomas Koenig<tkoenig@gcc.gnu.org>
>
> 	PR fortran/46405
> 	* invoke.texi:  Mention -ffree-line-length-none and
> 	-ffixed-line-length-none for preprocessing.

Yes, good idea.

Jerry
Thomas Koenig Jan. 8, 2011, 11:02 p.m. UTC | #2
Hi Jerry,

>> Hello world,
>>
>> I think that, after applying this doc patch, we can close PR 46405.
>> Tested with "make dvi", "make info" and "make pdf".
>>
>> OK for trunk?
>>
>>     Thomas
>>
>> 2011-01-08  Thomas Koenig<tkoenig@gcc.gnu.org>
>>
>>     PR fortran/46405
>>     * invoke.texi:  Mention -ffree-line-length-none and
>>     -ffixed-line-length-none for preprocessing.
> 
> Yes, good idea.

Sende          fortran/ChangeLog
Sende          fortran/invoke.texi
Übertrage Daten ..
Revision 168604 übertragen.

Thanks for the quick review!

	Thomas
diff mbox

Patch

Index: invoke.texi
===================================================================
--- invoke.texi	(Revision 168596)
+++ invoke.texi	(Arbeitskopie)
@@ -394,9 +394,11 @@ 
 To disable preprocessing of files with any of the above listed extensions,
 use the negative form: @option{-nocpp}.
 
-The preprocessor is run in traditional mode, be aware that any
-restrictions of the file-format, e.g. fixed-form line width,
-apply for preprocessed output as well.
+The preprocessor is run in traditional mode. Any restrictions of the
+file-format, especially the limits on line length, apply for
+preprocessed output as well, so it might be advisable to use the
+@option{-ffree-line-length-none} or @option{-ffixed-line-length-none}
+options.
 
 @item -dM
 @opindex @code{dM}