From: Doug Evans <xdje42@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>,
eliz@gnu.org
Subject: Re: [PATCH, doc RFA] Allow CLI and Python conditions to be set on same breakpoint
Date: Sun, 17 Nov 2013 17:59:00 -0000 [thread overview]
Message-ID: <CAP9bCMT+S8pG_EDQHPOK8fA+tR38keBXf=qAhpHcXS_VyT3Wrw@mail.gmail.com> (raw)
In-Reply-To: <8761rttr15.fsf@fleche.redhat.com>
On Fri, Nov 15, 2013 at 11:15 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <xdje42@gmail.com> writes:
>
> Doug> Need More Data.
>
> That goes both ways.
>
> If you still prefer the other semantics, perhaps you could explain why.
I don't prefer the other semantics.
Composing || with separate breakpoints is easy enough, and it's harder
to compose && (*1).
"works for me"
I was considering && early on, but got off track. Oh well.
---
(*1): The rest of the discussion seemed to be trying to imply there
was something more than this simple sentence involved in the
explanation, and I was trying to understand what.
prev parent reply other threads:[~2013-11-17 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 8:11 [commit] breakpoint.c (breakpoint_cond_eval): Fix and enhance comment Doug Evans
2013-11-14 17:58 ` [PATCH, doc RFA] Allow CLI and Python conditions to be set on same breakpoint Doug Evans
2013-11-14 18:44 ` Pedro Alves
2013-11-14 20:22 ` Phil Muldoon
2013-11-14 20:54 ` Tom Tromey
2013-11-14 21:21 ` Pedro Alves
2013-11-15 6:39 ` Doug Evans
2013-11-15 12:06 ` Pedro Alves
2013-11-15 16:30 ` Doug Evans
2013-11-15 16:45 ` Pedro Alves
2013-11-17 17:22 ` Doug Evans
2013-11-15 20:58 ` Tom Tromey
2013-11-17 17:59 ` Doug Evans [this message]
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='CAP9bCMT+S8pG_EDQHPOK8fA+tR38keBXf=qAhpHcXS_VyT3Wrw@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=pmuldoon@redhat.com \
--cc=tromey@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