Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 3/3] Move logic out of symbol_find_demangled_name
Date: Tue, 07 Jun 2016 14:03:00 -0000	[thread overview]
Message-ID: <fc8fa5a8-b9db-287f-ba8e-7464ac9e9bc9@redhat.com> (raw)
In-Reply-To: <86mvmywgj1.fsf@gmail.com>

On 06/06/2016 03:14 PM, Yao Qi wrote:
> Tom Tromey <tom@tromey.com> writes:
> 
>> > I'm not especially fond of the new name, "la_demangle_for_symbol".
>> >
> How about "la_sniff_by_symbol"?  IMO, symbol_find_demangled_name does
> two things, set the language of symbol, and get the demangled name.
> It is quite similar to frame unwinder sniffer and frame unwinding.
> 

I have to admit that it took me a bit to understand what the "by" meant,
but I think it intends to convey:

  "sniff the symbol's language from the symbol's mangled name".

So s/by symbol/from symbol/ would be better, IMHO.

symbol_find_demangled_name says:

/* (...) attempt to find any demangling algorithm that works and
   then set the language appropriately.  The returned name is allocated
   by the demangler and should be xfree'd.  */

So IMHO, something like "la_sniff_from_mangled_name" would be
even clearer.

BTW, what do we do with the resulting demangled name?  Is
there some sort of guideline for options to pass to the demangler?
Some sort of output that we're aiming for?

Thanks,
Pedro Alves


  parent reply	other threads:[~2016-06-07 14:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 14:49 [RFA 0/3] minor language cleanups Tom Tromey
2016-06-04 14:49 ` [RFA 1/3] Use VEC for filename_language_table Tom Tromey
2016-06-06 13:06   ` Yao Qi
2016-06-04 14:49 ` [RFA 3/3] Move logic out of symbol_find_demangled_name Tom Tromey
2016-06-06 14:15   ` Yao Qi
2016-06-07 11:41     ` Tom Tromey
2016-06-07 14:27       ` Pedro Alves
2016-06-07 15:12         ` Tom Tromey
2016-06-13 13:35           ` Pedro Alves
2016-06-17  8:28             ` Tom Tromey
2016-06-17 12:25               ` Pedro Alves
2016-06-17 12:36                 ` Tom Tromey
2016-06-17 13:50                   ` Pedro Alves
2016-06-24  3:15                     ` Tom Tromey
2016-06-07 14:03     ` Pedro Alves [this message]
2016-06-08  2:14       ` Tom Tromey
2016-06-08  4:03         ` Tom Tromey
2016-06-13 13:35           ` Pedro Alves
2016-06-17  8:41             ` Tom Tromey
2016-06-17 12:28               ` Pedro Alves
2016-06-04 14:49 ` [RFA 2/3] Move filename extensions into language_defn Tom Tromey
2016-06-06 13:23   ` Yao Qi
2016-06-06 21:04     ` Tom Tromey
2016-06-07 15:51       ` Yao Qi

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=fc8fa5a8-b9db-287f-ba8e-7464ac9e9bc9@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --cc=tom@tromey.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