From: Tom Tromey <tromey@redhat.com>
To: "André Pönitz" <andre.poenitz@nokia.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] 12843
Date: Mon, 29 Aug 2011 19:46:00 -0000 [thread overview]
Message-ID: <m3r544dmra.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201108290920.40589.andre.poenitz@nokia.com> (=?utf-8?Q?=22An?= =?utf-8?Q?dr=C3=A9_P=C3=B6nitz=22's?= message of "Mon, 29 Aug 2011 09:20:40 +0200")
Tom> (I'd like -break-insert to avoid linespecs completely, which would be a
Tom> big improvement IMO, ...
André> From an MI client's point of view, passing all location information as
André> a single argument is neither wanted nor needed.
Yeah. I am not sure why it works this way, as it seems to be against
the whole idea of MI.
André> or even require everything to be quoted as in
André> 25-break-insert --file "some thing.cpp" --line "794"
There's no need; MI already defines an input quoting syntax that is
sufficient.
Tom> ... but of course we still have to worry about compatibility.)
André> Just using new flags for the parameters should do the trick in this case.
André> In general, in the past, differences between different versions
André> of gdb have been large enough to require modifications in
André> consumer code anyway (both to take advantage of new features, and
André> to handle incompatibilities in input syntax), so requiring 100%
André> "feature" compatibility _just for the sake of it_ is unlikely to
André> be helpful. At least I would prefer a syntax with simple, uniform
André> quoting rules over ad-hoc solutions tied to a specific OS or file
André> system.
For MI, I don't think there is any issue. We can just add options to
-break-insert. (I don't know of anybody specifically working on this,
but I will at least put it in bugzilla.)
My view is that it is best to be compatible with existing "reasonable"
practice when possible, where "reasonable" means something akin to "has
actually happened".
In this case I think we can simplify linespec lexing without unduly
breaking things.
Tom> I think adopting these rules will make some of my ambiguous linespec
Tom> changes simpler.
André> I wonder whether it would be possible to just leave the current syntax
André> unchanged, and introduce a new, better behaved syntax and use some
André> global setting for toggling between them. So everybody concerned about
André> compatibility would not notice a change, and the others would put
André> 'set breakpoint syntax 2011' [or whatever]
André> in their .gdbinit and could use the new way.
My first reaction is against this, but I don't have a particularly good
explanation for that. I will think about it.
Tom
next prev parent reply other threads:[~2011-08-29 19:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 21:59 Keith Seitz
2011-08-26 18:23 ` Tom Tromey
2011-08-26 18:46 ` Keith Seitz
2011-08-26 19:07 ` Tom Tromey
2011-08-27 8:45 ` Eli Zaretskii
2011-08-27 13:17 ` asmwarrior
2011-08-29 19:18 ` Tom Tromey
2011-08-29 7:19 ` André Pönitz
2011-08-29 10:13 ` Pedro Alves
2011-08-29 12:06 ` Matt Rice
2011-08-29 12:15 ` André Pönitz
2011-08-29 13:53 ` Pedro Alves
2011-08-29 19:21 ` Jan Kratochvil
2011-08-30 8:19 ` André Pönitz
2011-08-30 9:21 ` Jan Kratochvil
2011-08-30 15:02 ` Tom Tromey
2011-08-30 16:34 ` André Pönitz
2011-08-30 17:21 ` Tom Tromey
2011-08-31 8:54 ` André Pönitz
2011-08-29 19:46 ` Tom Tromey [this message]
2011-08-29 21:13 ` Keith Seitz
2011-08-30 2:35 ` Daniel Jacobowitz
2011-08-30 15:00 ` Tom Tromey
2011-08-30 17:24 ` Tom Tromey
2011-08-31 18:17 ` Keith Seitz
2011-08-31 18:23 ` Jan Kratochvil
2011-08-31 18:52 ` Tom Tromey
2011-09-02 16:04 ` asmwarrior
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=m3r544dmra.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andre.poenitz@nokia.com \
--cc=gdb-patches@sourceware.org \
/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