--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-09
18:32 ---
The relevant part of the standard (C99: 6.10.3.2P2)
Otherwise, the original spelling of each preprocessing token in the argument is
retained in the
character string literal, except for special handling for
--- Additional Comments From s__nakayama at infoseek dot jp 2005-07-09
18:23 ---
(In reply to comment #4)
> Huh? I cannot reproduce it at all.
> with all of the versions of GCC I tried from 2.95.3 to 4.1.0 I get the
following:
> "\"\\\" \\\"\""
Did you confirm there was a tab in the
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-09
16:29 ---
Huh? I cannot reproduce it at all.
with all of the versions of GCC I tried from 2.95.3 to 4.1.0 I get the
following:
"\"\\\" \\\"\""
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22042
--- Additional Comments From s__nakayama at infoseek dot jp 2005-06-23
15:35 ---
(In reply to comment #1)
> I don't see why this is really a bug because if you output the string, it
will look the same.
NO! Your guess is wrong.
I never report, if the output always looks the same.
I wrot
--
What|Removed |Added
Known to fail||3.0.4 3.2.3 3.3.3 3.3.6
||3.4.4 4.0.0
Known to work|
--- Additional Comments From s__nakayama at infoseek dot jp 2005-06-14
07:20 ---
(In reply to comment #1)
Hmm, it does't look the same.
// test code
#define S(X) S2(X)
#define S2(X) #X
#define TAB " " /* 0x09 */
main()
{
puts(S(S(TAB)));
}
// GCC 4.0.0 result
"\"\011\""
// GCC 2.
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-13
12:36 ---
I don't see why this is really a bug because if you output the string, it will
look the same.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22042
