From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
Cc: Keith Seitz <keiths@redhat.com>,
asmwarrior <asmwarrior@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] Linespec rewrite: Parsing
Date: Mon, 26 Mar 2012 16:26:00 -0000 [thread overview]
Message-ID: <87r4wfs56s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAN9gPaG6brAESNAHgSUXmndtAno+MDBxd7idLZ0XMCG8qR_UJQ@mail.gmail.com> (Daniel Jacobowitz's message of "Sun, 25 Mar 2012 20:39:41 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <daniel.jacobowitz@gmail.com> writes:
Daniel> This is the change of behavior I think most likely to blow up.
Daniel> -break-insert proxies straight through to the CLI break command; have
Daniel> you checked what various other IDEs send today?
Daniel> Is a special case (yeah, I know) for a quoted function ending in
Daniel> :[0-9]* practical?
Keith, could you do this check?
I was hoping we could get away with this change. It seemed clearly sane
to me, but apparently front-end authors disagree :)
If it is just Code::Blocks, then it sounds like they have a fix already
and we could go forward.
For Plan B I think we can treat quotes differently and preserve
compatibility. I'd rather not do this, but I think compatibility is
more important than cleanliness.
Tom
next prev parent reply other threads:[~2012-03-26 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 21:21 Keith Seitz
2012-03-20 3:56 ` Eli Zaretskii
2012-03-20 5:31 ` Keith Seitz
2012-03-20 17:26 ` Eli Zaretskii
2012-03-24 13:03 ` asmwarrior
2012-03-24 17:23 ` Keith Seitz
2012-03-25 12:27 ` asmwarrior
2012-03-26 13:23 ` asmwarrior
2012-03-25 12:28 ` asmwarrior
2012-03-26 0:40 ` Daniel Jacobowitz
2012-03-26 16:26 ` Tom Tromey [this message]
2012-03-26 18:52 ` Keith Seitz
2012-03-26 19:05 ` André Pönitz
2012-03-26 19:31 ` Tom Tromey
2012-03-26 20:36 ` Keith Seitz
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=87r4wfs56s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=asmwarrior@gmail.com \
--cc=daniel.jacobowitz@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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