From: "Adam Butcher" <dev.lists@jessamine.co.uk>
To: "Jason Merrill" <jason@redhat.com>
Cc: dev.lists@jessamine.co.uk, gcc-patches@gcc.gnu.org
Subject: Re: [Patch] [C++0x] Support decltype-specifier as start of nested-name-specifier. (Bug 6709)
Date: Mon, 25 Jul 2011 09:20:00 -0000 [thread overview]
Message-ID: <3e4eb8314dd23ddcb02b8034ea51762c.squirrel@webmail.plus.net> (raw)
In-Reply-To: <4E29EA4A.7030809@redhat.com>
On Fri, July 22, 2011 10:23 pm, Jason Merrill wrote:
> On 07/21/2011 11:48 AM, Adam Butcher wrote:
>> No worries. I'm guilty of not checking mails for months due to other
>> commitments so didn't see either of your responses (or the committed
>> fix) on this decltype stuff until now.
>
> I was beginning to think you were dead or something, glad to see that's
> not the case. :)
>
:)
>>> Do you have tests for your decltype patches?
>>>
>> I assume you no longer need these as you've made your own on 176513
>> right?
>
> Yes, though they aren't terribly exhaustive if you have ideas about
> other variations we ought to test...
>
Just glanced over the changeset and looks like the tests are pretty much
equivalent to my own -- just spelt differently. Just building 4.7 head
now.
> Incidentally, the GNU copyright clerk told me that your copyright
> assignment isn't complete yet.
>
That's odd. I thought that was sorted ages ago around the time of the
old lambda branch fixes (pre 4.5) and the polymorphic lambda stuff. I
definitely sent the paperwork off. Who do I need to contact to sort
that out? I do intend to recreate the polymorphic lambda stuff against
4.7 at some point when I get some breathing time. The original patch no
longer fits and had some problems.
prev parent reply other threads:[~2011-07-25 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 17:08 Adam Butcher
2011-04-01 22:06 ` Jason Merrill
2011-07-21 15:59 ` Adam Butcher
2011-07-22 22:17 ` Jason Merrill
2011-07-25 9:20 ` Adam Butcher [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=3e4eb8314dd23ddcb02b8034ea51762c.squirrel@webmail.plus.net \
--to=dev.lists@jessamine.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).