public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r12-9975] libstdc++: Correctly call _string_types function
Date: Mon, 13 Nov 2023 15:45:23 +0000 (GMT)	[thread overview]
Message-ID: <20231113154523.09C053838A2D@sourceware.org> (raw)

https://gcc.gnu.org/g:cf5a6d8aa97bc361503ecfb07a5562d8b231eac8

commit r12-9975-gcf5a6d8aa97bc361503ecfb07a5562d8b231eac8
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed Oct 4 08:59:47 2023 -0600

    libstdc++: Correctly call _string_types function
    
    flake8 points out that the new call to _string_types from
    StdExpAnyPrinter.__init__ is not correct -- it needs to be qualified.
    
    libstdc++-v3/ChangeLog:
    
            * python/libstdcxx/v6/printers.py
            (StdExpAnyPrinter.__init__): Qualify call to
            _string_types.
    
    (cherry picked from commit 4bf77db70e2521dc89f9d7f51c7ae6e58a94b4f9)

Diff:
---
 libstdc++-v3/python/libstdcxx/v6/printers.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/python/libstdcxx/v6/printers.py b/libstdc++-v3/python/libstdcxx/v6/printers.py
index 51995b93806..ee25253d004 100644
--- a/libstdc++-v3/python/libstdcxx/v6/printers.py
+++ b/libstdc++-v3/python/libstdcxx/v6/printers.py
@@ -1298,7 +1298,7 @@ class StdExpAnyPrinter(SingleObjContainerPrinter):
             # FIXME need to expand 'std::string' so that gdb.lookup_type works
             if 'std::string' in mgrname:
                 mgrtypes = []
-                for s in _string_types():
+                for s in StdExpAnyPrinter._string_types():
                     try:
                         x = re.sub(r"std::string(?!\w)", s, m.group(1))
                         # The following lookup might raise gdb.error if the

                 reply	other threads:[~2023-11-13 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231113154523.09C053838A2D@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).