Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Markus Deuling <deuling@de.ibm.com>,
		GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdbserver/server.c: Replace 2x strlen() by a variable
Date: Thu, 21 Dec 2006 13:04:00 -0000	[thread overview]
Message-ID: <20061221130517.GH3640@adacore.com> (raw)
In-Reply-To: <25093.192.87.1.22.1166705194.squirrel@webmail.xs4all.nl>

> >  Actually, since the same string is duplicated a couple of times,
> >  I would also suggest declaring a constant string "QPassSignals:"
> >  and use the constant instead of risking a typo... How about:
> >
> >     const char str[] = "QPassSignals:";
> >
> >  and then use "sizeof (str) - 1". Is that bad coding style? Otherwise,
> >  you can declare your sale constant:
> >
> >     const int len = strlen (str);
> >
> >  I am not reviewer, so these are just suggestions, not a request (JIC).
> 
> I'm pretty sure GCC will optimize away the strlen("QPassSignals:") anyway,
> so we really shouldn't try to obfuscate the code just to make it a bit
> faster.  So if optimization was the Markus' argument for making this
> change I object to this change.

How about avoiding the string duplication? Do you object to that too?
This change seems like a good idea to me - although I agree that the
risks of inconsistency are very small...

-- 
Joel


  reply	other threads:[~2006-12-21 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  7:45 Markus Deuling
2006-12-21 11:08 ` Joel Brobecker
2006-12-21 11:48   ` Andreas Schwab
2006-12-21 12:47   ` Mark Kettenis
2006-12-21 13:04     ` Joel Brobecker [this message]
2006-12-26 15:35       ` Daniel Jacobowitz

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=20061221130517.GH3640@adacore.com \
    --to=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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