Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com,
	Fernando Nasser <fnasser@redhat.com>,
	Jim Blandy <jimb@redhat.com>
Subject: Re: [rfa] linespec.c, part 3
Date: Mon, 11 Nov 2002 17:15:00 -0000	[thread overview]
Message-ID: <15824.16252.683116.625849@localhost.redhat.com> (raw)
In-Reply-To: <ro1u1in1ykn.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > On Mon, 11 Nov 2002 17:28:45 -0500, Elena Zannoni <ezannoni@redhat.com> said:
 > > David Carlton writes:
 > 
 > >> This part of the decode_line_1 refactoring moves some code
 > >> initializing some flags into a separate function set_flags.  Some
 > >> comments:
 > 
 > > Looks ok, but I have a question. Wouldn't the code that sets up
 > > has_comma and is_quote_enclosed also belong to this set_flags
 > > function?
 > 
 > It seems entirely plausible to me that that is the case.  For now,
 > that will come in my next patch, which won't quite do what you ask:
 > the problem is that that part of the code is also updating 'p' to
 > figure out where a compound linespec separator is (for filenames or
 > C++/Java objects).  Teasing this apart is a bit of a mess; my current
 > "final" version of these changes has 'has_comma' buried in an internal
 > function, and 'is_quote_enclosed' doesn't last for very long.  But
 > it's messy, so I think that, once I'm done submitting patches that
 > just break off code into separate functions, we should revisit this
 > issue.
 > 

Yes, I didn't really think the issue through.

 > > (Ideally a struct of flags could be set up).
 > 
 > Yes, that would be a much better idea than passing the flag variables
 > by reference.
 > 
 > > But this is for a separate patch, you are just moving code around
 > > now.
 > 
 > Right.
 > 
 > > go ahead, thanks!
 > 
 > Committed.
 > 
 > (Now you've caught up to me!  Eek!  I'll have to get my grading done
 > quickly so I can keep up my end of things. :-) )
 > 

Don't worry, I have plenty of other things to do myself!

Elena


 > David Carlton
 > carlton@math.stanford.edu


  reply	other threads:[~2002-11-11 23:42 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 ` Klee Dienes
2002-11-11 17:15   ` Daniel Jacobowitz
2002-11-11 17:15     ` Klee Dienes
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 [this message]
  -- 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=15824.16252.683116.625849@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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