From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: RFA: another NEWS update
Date: Wed, 17 Feb 2010 20:35:00 -0000 [thread overview]
Message-ID: <m31vgjfvnl.fsf@fleche.redhat.com> (raw)
This updates NEWS to list all the Python API improvements since 7.0.
Ok?
Tom
2010-02-17 Tom Tromey <tromey@redhat.com>
* NEWS: Add Python API Improvements section.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.354
diff -u -r1.354 NEWS
--- NEWS 17 Feb 2010 20:08:24 -0000 1.354
+++ NEWS 17 Feb 2010 20:34:05 -0000
@@ -210,6 +210,20 @@
off, but this introduces a slight performance penalty. The default
is on.
+* Python API Improvements
+
+ ** GDB provides the new class gdb.LazyString. This is useful in
+ some pretty-printing cases. The new method gdb.Value.lazy_string
+ provides a simple way to create objects of this type.
+
+ ** The fields returned by gdb.Type.fields now have an
+ `is_base_class' attribute.
+
+ ** The new method gdb.Type.range returns the range of an array type.
+
+ ** The new method gdb.parse_and_eval can be used to parse and
+ evaluate an expression.
+
* New remote packets
QTDV
next reply other threads:[~2010-02-17 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:35 Tom Tromey [this message]
2010-02-18 4:09 ` Eli Zaretskii
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=m31vgjfvnl.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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