Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Small fixes to the Python API doc
Date: Mon, 20 Oct 2014 17:32:00 -0000	[thread overview]
Message-ID: <5445472A.9000200@ericsson.com> (raw)
In-Reply-To: <83k33z3lnd.fsf@gnu.org>

On 2014-10-16 02:38 PM, Eli Zaretskii wrote:
>> From: Simon Marchi <simon.marchi@ericsson.com>
>> CC: Simon Marchi <simon.marchi@ericsson.com>
>> Date: Thu, 16 Oct 2014 14:06:36 -0400
>>
>> First:
>> "Breakpoint.delete" is missing parenthesis.
> 
> I was going to say it doesn't need them, since it doesn't accept any
> arguments, but then I saw that we already use those empty parens
> everywhere.
> 
> So, reluctantly, OK for the parens.
> 
>>  @defvar Breakpoint.enabled
>>  This attribute is @code{True} if the breakpoint is enabled, and
>> -@code{False} otherwise.  This attribute is writable.
>> +@code{False} otherwise.  You can use it to enable or disable the breakpoint.
>> +This attribute is writable.
>>  @end defvar
> 
> The order is wrong: first say that it's writable, then that it can be
> used to enable/disable.
> 
> OK with that change.
> 
> Thanks.
> 

Thanks, pushed with your change:

commit fab3a15dfb4255e9d5a79536518ccdbed4e66e23
Author: Simon Marchi <simon.marchi@ericsson.com>
Date:   Mon Oct 20 13:29:36 2014 -0400

    Small fixes to the Python API doc

    First:
    "Breakpoint.delete" is missing parenthesis.

    Second:
    Someone on IRC asked, how come there is no disable() method in the
    Breakpoint object.  It turns out you have to do "bp.enabled = False".
    Since every normal person would probably search for "disable" in that page
    if their intent is to disable a python breakpoint, I thought it would be
    useful if the description contained "disable" so it would be easy to find.
    The result might seem a bit silly and redundant, so I am open to
    suggestions.

    gdb/doc/ChangeLog:

    	* python.texi (Breakpoints In Python): Add parenthesis after
    	Breakpoint.delete.  Clarify Breakpoint.enabled description so
    	that it	contains "disable".

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 474c1af..f1b2329 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2014-10-20  Simon Marchi  <simon.marchi@ericsson.com>
+
+	* python.texi (Breakpoints In Python): Add parenthesis after
+	Breakpoint.delete.  Clarify Breakpoint.enabled description so
+	that it contains "disable".
+
 2014-10-17  Doug Evans  <dje@google.com>

 	* python.texi (Events In Python): Document clear_objfiles event.
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 43663d8..f1fd841 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -4265,7 +4265,7 @@ watchpoint scope, the watchpoint remains valid even if execution of the
 inferior leaves the scope of that watchpoint.
 @end defun

-@defun Breakpoint.delete
+@defun Breakpoint.delete ()
 Permanently deletes the @value{GDBN} breakpoint.  This also
 invalidates the Python @code{Breakpoint} object.  Any further access
 to this object's attributes or methods will raise an error.
@@ -4273,7 +4273,8 @@ to this object's attributes or methods will raise an error.

 @defvar Breakpoint.enabled
 This attribute is @code{True} if the breakpoint is enabled, and
-@code{False} otherwise.  This attribute is writable.
+@code{False} otherwise.  This attribute is writable.  You can use it to enable
+or disable the breakpoint.
 @end defvar

 @defvar Breakpoint.silent


      reply	other threads:[~2014-10-20 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 18:06 Simon Marchi
2014-10-16 18:18 ` Phil Muldoon
2014-10-16 18:38 ` Eli Zaretskii
2014-10-20 17:32   ` Simon Marchi [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=5445472A.9000200@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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