From: David Carlton <carlton@math.stanford.edu>
To: Klee Dienes <klee@apple.com>
Cc: Jim Blandy <jimb@redhat.com>,
Fernando Nasser <fnasser@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: [rfa] linespec.c, part 3
Date: Mon, 11 Nov 2002 17:15:00 -0000 [thread overview]
Message-ID: <ro1wunj1ysa.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <35E8C110-F5C5-11D6-AA35-00039396EEB8@apple.com>
On Mon, 11 Nov 2002 17:30:41 -0500, Klee Dienes <klee@apple.com> said:
> The linespec.c changes you posted looked so cool, we couldn't resist
> using them.
Great! I would seem to have fans everywhere. :-)
> One issue that came up was that the part of our code that decodes an
> Objective-C function needs to have the if-clause removed from the
> breakpoint expression (since Objective-C functions can contain
> spaces). We did this by extending set_flags to pass back a pointer
> to the if-clause, if there was one, and by splitting decode_line_1
> into two functions, one of which sets the defaults, calls set_flags,
> strips off the if-clause and calls decode_line_2, which does the
> actual parsing.
I think that's pretty sensible. I don't care too much one way or
another as to whether or not there's a separate 'decode_line_2'
function to do the parsing, but the general idea of setting various
necessary flags first before doing any decoding sounds good to me.
For now, I want to worry about breaking up the existing code into
separate functions first (I'm already giving Elena enough to worry
about as it is, I think), but it sounds like, once that phase is done
and we can actually understand what decode_line_1 is doing, we'll want
to start rewriting functions, changing the existing reorganization.
So hold off on your patch until then, and then we can talk.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-11-11 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 17:15 David Carlton
2002-11-11 17:15 ` Elena Zannoni
2002-11-11 17:15 ` David Carlton
2002-11-11 17:15 ` Elena Zannoni
2002-11-11 17:15 ` Klee Dienes
2002-11-11 17:15 ` Daniel Jacobowitz
2002-11-11 17:15 ` Klee Dienes
2002-11-11 17:15 ` David Carlton [this message]
2002-11-11 17:15 David Carlton
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=ro1wunj1ysa.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=klee@apple.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