From: "Adam Fedor" <fedor@doc.com>
To: "Klee Dienes" <klee@apple.com>, "Jim Blandy" <jimb@redhat.com>
Cc: "Michael Snyder" <msnyder@redhat.com>, <gdb-patches@sources.redhat.com>
Subject: RE: [PATCH] Redefine skip_quoted
Date: Mon, 14 Oct 2002 16:17:00 -0000 [thread overview]
Message-ID: <E5F2FFE55E362144876F14CB0AEE71392100EC@exchange1.urp.doc.com> (raw)
> From: Klee Dienes [mailto:klee@apple.com]
>
> 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.
>
> Here's the appropriate diff from our linespec.c:
>
In the patch I made also, the only place this change is used is in decode_line_1. I must say that 99% of the problems I had getting Objective-C to work in gdb on multiple platforms was in this function. It's a nightmare, at least for Objective-C method names.
next reply other threads:[~2002-10-14 23:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 16:17 Adam Fedor [this message]
-- strict thread matches above, loose matches on Subject: below --
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-17 23:33 ` Adam Fedor
2002-10-18 14:52 ` Elena Zannoni
2002-10-18 15:54 ` Adam Fedor
2002-10-22 8:04 ` Elena Zannoni
2002-10-25 12:43 ` Adam Fedor
2002-11-03 16:20 ` Elena Zannoni
2002-11-07 12:36 ` Jim Blandy
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=E5F2FFE55E362144876F14CB0AEE71392100EC@exchange1.urp.doc.com \
--to=fedor@doc.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