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: gdb-patches@sources.redhat.com,
	Elena Zannoni <ezannoni@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.12061.128364.623571@localhost.redhat.com> (raw)
In-Reply-To: <ro17kfj3hxd.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > [ Sorry about that almost-empty message a few minutes ago. ]
 > 
 > 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? (Ideally a struct of flags could be set up). I see that
has_comma plays the same trick with changing the char before parsing
and restoring it afterwards. :-( I wonder if this could be changed by
using a comma_ptr pointer and changing the for loop to continue until
the comma_ptr instead of up to '\0'.  Or just duplicate the first half
of the string and play with that, it's not that we would be using a
lot more memory, and it would seem less fragile than relying on a
comment pleading you not to change 'ii'. Smae could be said for the
current use of 'ii' with 'if'. But this is for a separate patch, you
are just moving code around now.

 > * The current code sets a flag 'has_parens' to indicate whether or not
 >   there is a paren, and a variable 'pp' to store the location of that
 >   paren.  This is redundant; we might as well have 'pp' indicate both
 >   parts of that data, where pp is NULL if has_parens would be 0 and pp
 >   isn't NULL if has_parens would be one.  Given that I'd rather pass
 >   as few variables by reference as possible, I decided to go that way;
 >   I've named the resulting variable 'paren_pointer', and updated
 >   references to either 'has_parens' or 'pp' accordingly.
 > 

good move.

 > * The current code uses the variable 'ii' both within the code that
 >   I've extracted and elsewhere.  But those uses are distinct: in fact,
 >   the value of 'ii' is changed immediately after the code that this
 >   patch extracts.  
 > 

ok.

go ahead, thanks!

Elena


 > David Carlton
 > carlton@math.stanford.edu
 > 
 > 2002-11-11  David Carlton  <carlton@math.stanford.edu>
 > 
 > 	* linespec.c (set_flags): New function.
 > 	(decode_line_1): Move code into set_flags.
 > 
 > Index: linespec.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/linespec.c,v
 > retrieving revision 1.27
 > diff -u -p -r1.27 linespec.c
 > --- linespec.c	11 Nov 2002 21:18:55 -0000	1.27
 > +++ linespec.c	11 Nov 2002 21:29:39 -0000
 > @@ -42,6 +42,8 @@ extern char *operator_chars (char *, cha
 >  static void initialize_defaults (struct symtab **default_symtab,
 >  				 int *default_line);
 >  
 > +static void set_flags (char *arg, int *is_quoted, char **paren_pointer);
 > +
 >  static struct symtabs_and_lines decode_indirect (char **argptr);
 >  
 >  static void cplusplus_error (const char *name, const char *fmt, ...) ATTR_FORMAT (printf, 2, 3);
 > @@ -528,7 +530,7 @@ decode_line_1 (char **argptr, int funfir
 >    struct symtabs_and_lines values;
 >    struct symtab_and_line val;
 >    register char *p, *p1;
 > -  char *q, *pp, *ii, *p2;
 > +  char *q, *ii, *p2;
 >  #if 0
 >    char *q1;
 >  #endif
 > @@ -542,10 +544,13 @@ decode_line_1 (char **argptr, int funfir
 >    char *copy;
 >    struct symbol *sym_class;
 >    int i1;
 > +  /* This is NULL if there are no parens in *ARGPTR, or a pointer to
 > +     the closing parenthesis if there are parens.  */
 > +  char *paren_pointer;
 > +  /* This says whether or not something in *ARGPTR is quoted with
 > +     completer_quotes (i.e. with single quotes).  */
 >    int is_quoted;
 >    int is_quote_enclosed;
 > -  int has_parens;
 > -  int has_if = 0;
 >    int has_comma = 0;
 >    struct symbol **sym_arr;
 >    struct type *t;
 > @@ -563,45 +568,13 @@ decode_line_1 (char **argptr, int funfir
 >    if (**argptr == '*')
 >      return decode_indirect (argptr);
 >  
 > -  /* 'has_if' is for the syntax:
 > -   *     (gdb) break foo if (a==b)
 > -   */
 > -  if ((ii = strstr (*argptr, " if ")) != NULL ||
 > -      (ii = strstr (*argptr, "\tif ")) != NULL ||
 > -      (ii = strstr (*argptr, " if\t")) != NULL ||
 > -      (ii = strstr (*argptr, "\tif\t")) != NULL ||
 > -      (ii = strstr (*argptr, " if(")) != NULL ||
 > -      (ii = strstr (*argptr, "\tif( ")) != NULL)
 > -    has_if = 1;
 > -  /* Temporarily zap out "if (condition)" to not
 > -   * confuse the parenthesis-checking code below.
 > -   * This is undone below. Do not change ii!!
 > -   */
 > -  if (has_if)
 > -    {
 > -      *ii = '\0';
 > -    }
 > -
 >    /* Set various flags.
 > -   * 'has_parens' is important for overload checking, where
 > +   * 'paren_pointer' is important for overload checking, where
 >     * we allow things like: 
 >     *     (gdb) break c::f(int)
 >     */
 >  
 > -  /* Maybe arg is FILE : LINENUM or FILE : FUNCTION */
 > -
 > -  is_quoted = (**argptr
 > -	       && strchr (get_gdb_completer_quote_characters (),
 > -			  **argptr) != NULL);
 > -
 > -  has_parens = ((pp = strchr (*argptr, '(')) != NULL
 > -		&& (pp = strrchr (pp, ')')) != NULL);
 > -
 > -  /* Now that we're safely past the has_parens check,
 > -   * put back " if (condition)" so outer layers can see it 
 > -   */
 > -  if (has_if)
 > -    *ii = ' ';
 > +  set_flags (*argptr, &is_quoted, &paren_pointer);
 >  
 >    /* Maybe we were called with a line range FILENAME:LINENUM,FILENAME:LINENUM
 >       and we must isolate the first half.  Outer layers will call again later
 > @@ -682,7 +655,7 @@ decode_line_1 (char **argptr, int funfir
 >    if (has_comma)
 >      *ii = ',';
 >  
 > -  if ((p[0] == ':' || p[0] == '.') && !has_parens)
 > +  if ((p[0] == ':' || p[0] == '.') && paren_pointer == NULL)
 >      {
 >        /*  C++ */
 >        /*  ... or Java */
 > @@ -1075,9 +1048,9 @@ decode_line_1 (char **argptr, int funfir
 >        if (p[-1] != '\'')
 >  	error ("Unmatched single quote.");
 >      }
 > -  else if (has_parens)
 > +  else if (paren_pointer != NULL)
 >      {
 > -      p = pp + 1;
 > +      p = paren_pointer + 1;
 >      }
 >    else
 >      {
 > @@ -1214,6 +1187,46 @@ initialize_defaults (struct symtab **def
 >        *default_symtab = cursal.symtab;
 >        *default_line = cursal.line;
 >      }
 > +}
 > +
 > +static void
 > +set_flags (char *arg, int *is_quoted, char **paren_pointer)
 > +{
 > +  char *ii;
 > +  int has_if = 0;
 > +
 > +  /* 'has_if' is for the syntax:
 > +   *     (gdb) break foo if (a==b)
 > +   */
 > +  if ((ii = strstr (arg, " if ")) != NULL ||
 > +      (ii = strstr (arg, "\tif ")) != NULL ||
 > +      (ii = strstr (arg, " if\t")) != NULL ||
 > +      (ii = strstr (arg, "\tif\t")) != NULL ||
 > +      (ii = strstr (arg, " if(")) != NULL ||
 > +      (ii = strstr (arg, "\tif( ")) != NULL)
 > +    has_if = 1;
 > +  /* Temporarily zap out "if (condition)" to not
 > +   * confuse the parenthesis-checking code below.
 > +   * This is undone below. Do not change ii!!
 > +   */
 > +  if (has_if)
 > +    {
 > +      *ii = '\0';
 > +    }
 > +
 > +  *is_quoted = (*arg
 > +		&& strchr (get_gdb_completer_quote_characters (),
 > +			   *arg) != NULL);
 > +
 > +  *paren_pointer = strchr (arg, '(');
 > +  if (*paren_pointer != NULL)
 > +    *paren_pointer = strrchr (*paren_pointer, ')');
 > +
 > +  /* Now that we're safely past the paren_pointer check,
 > +   * put back " if (condition)" so outer layers can see it 
 > +   */
 > +  if (has_if)
 > +    *ii = ' ';
 >  }
 >  
 >  \f


  parent reply	other threads:[~2002-11-11 22:33 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   ` David Carlton
2002-11-11 17:15   ` Daniel Jacobowitz
2002-11-11 17:15     ` Klee Dienes
2002-11-11 17:15 ` Elena Zannoni [this message]
2002-11-11 17:15   ` David Carlton
2002-11-11 17:15     ` Elena Zannoni
  -- 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.12061.128364.623571@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