From: Dodji Seketeli <dodji@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PR c++/141777
Date: Thu, 19 Nov 2009 18:27:00 -0000 [thread overview]
Message-ID: <20091119181540.GA9253@adjoa.torimasen.com> (raw)
In-Reply-To: <4B056E3A.4060606@redhat.com>
On Thu, Nov 19, 2009 at 11:11:38AM -0500, Jason Merrill wrote:
> I was thinking that we didn't need a new tree node, just change the
> template_info fields in lang_decl_min and lang_type_class to be a new
> type, i.e. a pointer to your template_info_s.
The reason why I went for a tree node is that quite some places expect
template_info to be a tree. So it was much easier to just wrap it in a tree.
Should I go ahead nevertheless and use template_info_s instead?
Dodji
next prev parent reply other threads:[~2009-11-19 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 22:13 Dodji Seketeli
2009-11-17 1:33 ` Jason Merrill
2009-11-17 13:23 ` Dodji Seketeli
2009-11-17 20:48 ` Jason Merrill
2009-11-19 14:27 ` Dodji Seketeli
2009-11-19 16:13 ` Jason Merrill
2009-11-19 18:16 ` Dodji Seketeli
2009-11-19 18:27 ` Dodji Seketeli [this message]
2009-11-19 20:26 ` Jason Merrill
2009-11-20 8:37 ` Dodji Seketeli
2009-11-20 15:00 ` Jason Merrill
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=20091119181540.GA9253@adjoa.torimasen.com \
--to=dodji@redhat.com \
--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).