From: Doug Evans <dje@google.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: [patch] gdbserver: Add support for Z0/Z1 packets
Date: Wed, 24 Jun 2009 19:01:00 -0000 [thread overview]
Message-ID: <e394668d0906241201l7d763f34pedb1ad98cc50158c@mail.gmail.com> (raw)
In-Reply-To: <4A427584.2090908@qnx.com>
On Wed, Jun 24, 2009 at 11:50 AM, Aleksandar
Ristovski<aristovski@qnx.com> wrote:
> I did not do any renaming - I think it is not terribly confusing since both
> in target.h comment and server.c 'Z' case it is made very clear that it
> handles both breakpoints and watchpoints (i.e. I don't find it any clearer
> if it was called "insert_point"... it would still require reading the
> comment in target.h)
fwiw, I think the naming is important. People come at the source from
various angles, starting points, and contexts. I can imagine someone
getting tripped up (i.e. spending time doing something that they
otherwise wouldn't have) by reading "insert_watchpoint" and not
knowing it also applied to breakpoints. Good names are important. (or
at least not obviously problematic names; picking good names is
sometimes hard, for me anyway).
My $0.02.
next prev parent reply other threads:[~2009-06-24 19:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 1:20 Aleksandar Ristovski
2009-06-17 1:35 ` Aleksandar Ristovski
2009-06-19 7:08 ` Doug Evans
2009-06-19 13:56 ` Aleksandar Ristovski
2009-06-20 22:01 ` Pedro Alves
2009-06-22 19:39 ` Aleksandar Ristovski
2009-06-22 22:46 ` Pedro Alves
2009-06-23 15:18 ` Aleksandar Ristovski
2009-06-23 15:59 ` Pedro Alves
2009-06-23 16:57 ` Aleksandar Ristovski
2009-06-24 18:51 ` Aleksandar Ristovski
2009-06-24 19:01 ` Doug Evans [this message]
2009-06-24 19:04 ` Aleksandar Ristovski
2009-06-24 19:10 ` Doug Evans
2009-06-24 19:10 ` Pedro Alves
2009-06-24 19:20 ` Aleksandar Ristovski
2009-06-24 19:28 ` Pedro Alves
2009-06-24 19:25 ` Aleksandar Ristovski
2009-06-25 22:18 ` Pedro Alves
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=e394668d0906241201l7d763f34pedb1ad98cc50158c@mail.gmail.com \
--to=dje@google.com \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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