From: Adam Fedor <fedor@doc.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, Klee Dienes <klee@apple.com>,
Michael Snyder <msnyder@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Redefine skip_quoted
Date: Fri, 18 Oct 2002 15:54:00 -0000 [thread overview]
Message-ID: <3DB09113.9070205@doc.com> (raw)
In-Reply-To: <15792.33251.884402.152637@localhost.redhat.com>
Elena Zannoni wrote:
> Adam Fedor writes:
> > Jim Blandy wrote:
> > > Klee Dienes <klee@apple.com> writes:
> > >
> > >>In the Apple code, we use skip_quoted to allow for the possibility of
> > >>spaces in Objective-C function names.
> > >>
> > >>I'm actually coming to think that allowing people to break on unquoted
> > >>Objective-C methods was a mistake: it's caused us no end of trouble
> > >>trying to shoehorn decode_line_1() into handling every possible
> > >>edge-case. I'm not sure how practical it is for us to remove it at
> > >>this point, though --- we'd have to do some research among our
> > >>Objective-C developers to find out how important a feature it is to
> > >>them, I think.
> > >
> > >
> > > So, the original patch posted is preparation for a behavior which you
> > > now suspect was a mistake, and which has caused you no end of trouble?
> > > (Or do I have the sense of what you were saying reversed?) You can
> > > forgive me if hearing that makes me a bit hesitant to approve the
> > > patch, right? :)
> > >
> >
> > Well, really the use of skip_quoted for ObjC (in a patch that I haven't
> > submitted yet), really has more to do with handling the canonical form
> > of an Objective-C method symbol (e.g. -[MyObject myMethod:arg2:]) that
> > comes from objc-lang.c. Most of the breakpoint cases that a user would
> > enter are handled elsewhere (in a patch that I also haven't submitted).
> >
>
> I have to agree with Jim here, I think we should wait on the parts you
> haven't submitted before deciding on this one. Could you just have
> added the chars you need to the gdb_completer_word_break_characters
> variable?
>
No. It involves removing characters. Another option would be to define a
new function, say skip_objc_quoted, just for objc which would be similar
to skip_quoted. How about that?
--
Adam Fedor, Digital Optics Corp. | I'm glad I hate spinach, because
http://www.doc.com | if I didn't, I'd eat it, and you
| know how I hate the stuff.
next prev parent reply other threads:[~2002-10-18 22:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 19:53 Adam Fedor
2002-10-08 16:22 ` Michael Snyder
2002-10-14 13:47 ` Jim Blandy
2002-10-14 14:30 ` Michael Snyder
2002-10-14 14:33 ` Klee Dienes
2002-10-16 0:44 ` Jim Blandy
2002-10-16 3:29 ` [PATCH] minor nit in read_tilde_fields Klee Dienes
2002-10-16 6:54 ` Daniel Jacobowitz
2002-10-17 23:33 ` [PATCH] Redefine skip_quoted Adam Fedor
2002-10-18 14:52 ` Elena Zannoni
2002-10-18 15:54 ` Adam Fedor [this message]
2002-10-22 8:04 ` Elena Zannoni
2002-10-25 12:43 ` Adam Fedor
2002-11-03 16:20 ` Elena Zannoni
2002-11-03 18:54 ` GDB ObjC plan (was: Re: [PATCH] Redefine skip_quoted) Adam Fedor
2002-11-07 12:36 ` [PATCH] Redefine skip_quoted Jim Blandy
2002-10-14 16:17 Adam Fedor
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=3DB09113.9070205@doc.com \
--to=fedor@doc.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=klee@apple.com \
--cc=msnyder@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