From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [rfc] Be in language c more c++ compatible
Date: Mon, 25 Jul 2011 15:00:00 -0000 [thread overview]
Message-ID: <m3y5zmtoao.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201107231838.p6NIcBDq020651@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Sat, 23 Jul 2011 20:38:11 +0200 (CEST)")
Jan> The first (c-exp.y) part parses those parts of `language c++' which cannot
Jan> (I believe - RFC) lead to misinterpretation of any valid C code even in
Jan> `language c'.
Mark> I think this is a bad idea.
For the best results, one must also provide reasons why it is a bad
idea. Otherwise when looking at the pros and cons, your dislike appears
in the cons list as merely a personal dislike -- which while not
unimportant certainly carries much less weight than technical arguments.
Tom
next prev parent reply other threads:[~2011-07-25 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 20:47 Jan Kratochvil
2011-07-16 8:42 ` Tom Tromey
2011-07-16 9:45 ` Jan Kratochvil
2011-07-23 21:17 ` Mark Kettenis
2011-07-23 21:38 ` Jan Kratochvil
2011-07-25 15:00 ` Tom Tromey [this message]
2011-07-23 22:12 ` Matt Rice
2011-07-24 15:59 ` Jan Kratochvil
2011-07-24 15:59 ` Matt Rice
2011-07-25 14:52 ` Tom Tromey
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=m3y5zmtoao.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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