From: Diego Novillo <dnovillo@google.com>
To: Richard Henderson <rth@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Gabriel Dos Reis <gdr@integrable-solutions.net>,
gcc-patches@gcc.gnu.org, laurynas.biveinis@gmail.com,
Lawrence Crowl <crowl@google.com>
Subject: Re: [cxx-conversion] Support garbage-collected C++ templates
Date: Fri, 10 Aug 2012 20:41:00 -0000 [thread overview]
Message-ID: <502571F1.20205@google.com> (raw)
In-Reply-To: <50256B94.4070201@redhat.com>
On 12-08-10 16:14 , Richard Henderson wrote:
> On 2012-08-10 08:06, Diego Novillo wrote:
>> The end point should be that the only thing we really need to tell
>> gengtype about are the variable roots. Everything else would rely on
>> user-provided markings. I suppose we could still keep the automatic
>> option for really simple stuff, though.
>
> Yes please. Markup may be awkward, but I think can be less awkward
> than generating those three cookie-cutter functions.
Yeah. Another thing I suppose we want to keep is the whole 'prev' and
'next' markings. These generate harness that would be cumbersome to
implement from user code.
Diego.
next prev parent reply other threads:[~2012-08-10 20:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 19:53 Diego Novillo
2012-08-08 20:13 ` Gabriel Dos Reis
2012-08-08 20:37 ` Diego Novillo
2012-08-08 20:47 ` Gabriel Dos Reis
2012-08-08 20:58 ` Diego Novillo
2012-08-08 21:25 ` Gabriel Dos Reis
2012-08-08 21:27 ` Diego Novillo
2012-08-08 21:29 ` Gabriel Dos Reis
2012-08-09 9:03 ` Richard Guenther
2012-08-09 12:44 ` Diego Novillo
2012-08-09 13:05 ` Richard Guenther
2012-08-10 15:07 ` Diego Novillo
2012-08-10 20:14 ` Richard Henderson
2012-08-10 20:41 ` Diego Novillo [this message]
2012-08-11 1:27 ` Lawrence Crowl
2023-07-05 10:21 ` GTY: Repair 'enum gty_token', 'token_names' desynchronization (was: [cxx-conversion] Support garbage-collected C++ templates) Thomas Schwinge
2023-07-06 6:01 ` Richard Biener
2012-08-09 7:12 ` [cxx-conversion] Support garbage-collected C++ templates Laurynas Biveinis
2012-08-10 16:14 ` Diego Novillo
2012-08-13 3:28 ` Laurynas Biveinis
2012-08-13 13:40 ` Diego Novillo
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=502571F1.20205@google.com \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=laurynas.biveinis@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=rth@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).