This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH v3 3/3] Port libstdc++ pretty-printers to Python 2 + Python 3
- From: Tom Tromey <tromey at redhat dot com>
- To: Samuel Bronson <naesten at gmail dot com>
- Cc: libstdc++ at gcc dot gnu dot org, GCC Patches <gcc-patches at gcc dot gnu dot org>, Jonathan Wakely <jwakely at redhat dot com>, GDB Patches <gdb-patches at sourceware dot org>, Matthias Klose <doko at ubuntu dot com>
- Date: Wed, 30 Jul 2014 08:03:43 -0600
- Subject: Re: [PATCH v3 3/3] Port libstdc++ pretty-printers to Python 2 + Python 3
- Authentication-results: sourceware.org; auth=none
- References: <1400701554-18062-1-git-send-email-naesten at gmail dot com> <1405046899-32639-1-git-send-email-naesten at gmail dot com> <1405046899-32639-4-git-send-email-naesten at gmail dot com> <8761j4imol dot fsf at naesten dot mooo dot com> <87tx6asm4y dot fsf at fleche dot redhat dot com> <87k370685j dot fsf at naesten dot mooo dot com>
>> I don't think this comment is applicable.
>> The libstdc++ pretty-printers use gdb.Value.lazy_string, not the
>> built-in Python types.
Samuel> Hmm, doesn't that just make it a timebomb -- a value that will
Samuel> explode if, at some point in the future, someone tries to treat
Samuel> it as a string?
I don't think so.
The results from the pretty-printer, when called from gdb, are generally
either printed or discarded.
In any case the comment still doesn't seem correct.