This is the mail archive of the gcc@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: fdump-ast-original and strg:

From: Florian Krohm <florian at edamail dot fishkill dot ibm dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Guillaume <guillaume dot thouvenin at polymtl dot ca>, Joe Buck <jbuck at synopsys dot com>, gcc at gcc dot gnu dot org
Date: Fri, 30 Nov 2001 13:54:44 -0500
Subject: Re: fdump-ast-original and strg:
References: <Pine.LNX.4.33L2.0111301216140.1619-100000@leffetriple.localdomain> <01113013120701.01459@warp9.fishkill.ibm.com> <20011130102600.A20309@codesourcery.com>

>
> "\0122" will work fine.  (Or, in this case, "\n2" assuming ASCII.)
>
Yup, you're right. So if you use octal notation to represent a 
non-printable character and always use 3 octal digits following
the '\' you have something that should work in all cases.

> We already have code to emit strings safely, into the assembly output;
> you could just use that.
>
Even better!

Florian

Follow-Ups:
- Re: fdump-ast-original and strg:
  - From: Joe Buck

References:
- Re: fdump-ast-original and strg:
  - From: Guillaume
- Re: fdump-ast-original and strg:
  - From: Florian Krohm
- Re: fdump-ast-original and strg:
  - From: Zack Weinberg

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