This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gfortran,patch] add -fbackslash
- From: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>
- To: FX Coudert <fxcoudert at gmail dot com>
- Cc: gfortran <fortran at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 20 Jun 2005 20:21:51 +0200
- Subject: Re: [gfortran,patch] add -fbackslash
- References: <42B5E36C.8060101@gmail.com>
FX Coudert wrote:
> Index: invoke.texi
> ===================================================================
> RCS file: /cvsroot/gcc/gcc/gcc/fortran/invoke.texi,v
> retrieving revision 1.16
> diff -u -3 -p -r1.16 invoke.texi
> --- invoke.texi 5 Jun 2005 13:13:09 -0000 1.16
> +++ invoke.texi 19 Jun 2005 20:56:36 -0000
> @@ -208,6 +208,15 @@ Do nothing if this is already the defaul
> @cindex character set
> Allow @samp{$} as a valid character in a symbol name.
>
> +@cindex -fbackslash option
> +@cindex options, -fbackslash
> +@item -fbackslash
> +@cindex backslash
> +@cindex escape characters
> +@item
> +Compile switch for changing the interpretation of a backslash from a
> +character to ``C''-style escape characters.
> +
> @cindex -ffixed-line-length-@var{n} option
> @cindex options, -ffixed-line-length-@var{n}
> @item -ffixed-line-length-@var{n}
We default to -fbackslash, so you should document -fno-backslash. (Not in
lang.opt, though. The convention seems to be the other way round there.
Apart from that, this is of course ok
- Tobi