From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org, eliz@gnu.org, pmuldoon@redhat.com
Subject: [PATCH 1/4] Fix some aspects of python lazy string handling: docs
Date: Mon, 07 Nov 2016 01:12:00 -0000 [thread overview]
Message-ID: <94eb2c1131b4d391aa0540abb830@google.com> (raw)
Hi. This patch is a small doc fix to note that arrays can be
turned into lazy strings as well as pointers.
2016-11-06 Doug Evans <dje@google.com>
* guile.texi (Lazy Strings In Guile): Mention arrays.
* python.texi (Lazy Strings In Python): Ditto.
diff --git a/gdb/doc/guile.texi b/gdb/doc/guile.texi
index 0030f3f..65bc008 100644
--- a/gdb/doc/guile.texi
+++ b/gdb/doc/guile.texi
@@ -3248,7 +3248,7 @@ most appropriate encoding when the string is printed.
@deffn {Scheme Procedure} lazy-string-type lazy-string
Return the type that is represented by @var{lazy-string}'s type.
-For a lazy string this will always be a pointer type. To
+For a lazy string this is a pointer or array type. To
resolve this to the lazy string's character type, use
@code{type-target-type}.
@xref{Types In Guile}.
@end deffn
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index d6507e5..834247c 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -4884,7 +4884,7 @@ is not writable.
@defvar LazyString.type
This attribute holds the type that is represented by the lazy string's
-type. For a lazy string this will always be a pointer type. To
+type. For a lazy string this is a pointer or array type. To
resolve this to the lazy string's character type, use the type's
@code{target} method. @xref{Types In Python}. This attribute is not
writable.
next reply other threads:[~2016-11-07 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 1:12 Doug Evans [this message]
2016-11-07 3:36 ` Eli Zaretskii
2017-03-16 16:40 ` Doug Evans via gdb-patches
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=94eb2c1131b4d391aa0540abb830@google.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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