Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Klee Dienes <klee@apple.com>
Cc: David Carlton <carlton@math.stanford.edu>,
	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: <20021111225612.GA28829@nevyn.them.org> (raw)
In-Reply-To: <35E8C110-F5C5-11D6-AA35-00039396EEB8@apple.com>

On Mon, Nov 11, 2002 at 05:30:41PM -0500, Klee Dienes wrote:
> I'm not sure if you want to deal with this now, or if you'd rather I 
> wait until you're done with merging your changes, but I figured I'd 
> mention it now while you were looking at set_flags stuff:
> 
> The linespec.c changes you posted looked so cool, we couldn't resist 
> using them.  So rather than try to deal with the merge conflicts from 
> the upcoming stream of linespec.c patches, we decided to re-add our 
> Objective-C support to the linespec.c from your branch and use that as 
> our linespec.c.
> 
> 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.

Dare I ask what you did with the existing decode_line_2, also in that
file?  Other than that, it looks reasonable...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-11-11 22:55 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 [this message]
2002-11-11 17:15     ` Klee Dienes
2002-11-11 17:15   ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
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=20021111225612.GA28829@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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