From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: Foo<int,(char*)&string>
Date: Wed, 18 Feb 2004 00:20:00 -0000 [thread overview]
Message-ID: <yf2k72l62lt.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040217022008.24CA64B104@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 16 Feb 2004 21:20:08 -0500 (EST)")
On Mon, 16 Feb 2004 21:20:08 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:
> The second template parameter is a "char *"; a value, not a type.
> gcc 3.3.2 -gstabs+ emits this:
> .stabs "Foo<int,&string>:Tt(1,1)=..."
> gcc HEAD -gstabs+ just changed to emit this:
> .stabs "Foo<int,(char*)(&string)>:Tt(0,25)=..."
> Do we care? I think the "(char*)(&string)" looks ugly but is legal.
> I want to change templates.exp to accept this as a PASS.
Sounds good to me.
David Carlton
carlton@kealia.com
prev parent reply other threads:[~2004-02-18 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 2:20 Foo<int,(char*)&string> Michael Elizabeth Chastain
2004-02-17 2:44 ` Foo<int,(char*)&string> Daniel Jacobowitz
2004-02-18 0:20 ` David Carlton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yf2k72l62lt.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox