From: Tom Tromey <tromey@redhat.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] Fix for D demangling in GDB
Date: Fri, 10 Jan 2014 21:43:00 -0000 [thread overview]
Message-ID: <87r48f4io8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CABOHX+dKwZghfF=2KRD8Znj3B5s=knOAdX9VZKBH+8CVBAT1NA@mail.gmail.com> (Iain Buclaw's message of "Fri, 10 Jan 2014 14:51:50 +0000")
>>>>> "Iain" == Iain Buclaw <ibuclaw@gdcproject.org> writes:
Iain> Couldn't find an easy way to move, then fix. So I did fix, then move.
Thank you.
Iain> +/* Demangle the calling convention from MANGLE and append it to TEMPBUF.
Iain> + Return the remaining string on success or NULL on failure. */
Iain> +static const char *
Iain> +parse_call_convention (struct obstack *tempbuf, const char *mangle)
Blank line between comment and start of function; here and elsewhere.
Iain> +}
Iain> +
Iain> static int
Iain> -extract_type_info (const char *mangled_str, struct obstack *tempbuf)
Iain> +call_convention_p (const char *mangle)
Iain> {
Needs an intro comment.
Iain> + if (mangle && call_convention_p (mangle))
We're trying to use the explicit checking form these days, so
"if (mangle != NULL && ..."
I didn't check the rest of the patch for this nit -- could you take a
look?
Other than the nits and the remaining test suite thing, this looks good.
Thanks again for splitting the patch.
Tom
next prev parent reply other threads:[~2014-01-10 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 13:13 Iain Buclaw
2014-01-09 21:54 ` Tom Tromey
2014-01-10 13:24 ` Iain Buclaw
2014-01-10 14:51 ` Iain Buclaw
2014-01-10 21:43 ` Tom Tromey [this message]
2014-01-11 20:08 ` Iain Buclaw
2014-01-10 15:05 ` Iain Buclaw
2014-01-10 21:45 ` Tom Tromey
2014-01-11 20:18 ` Iain Buclaw
2014-01-13 20:04 ` Tom Tromey
2014-01-18 18:24 ` Iain Buclaw
2014-01-10 21:22 ` Tom Tromey
2014-01-10 23:09 ` Iain Buclaw
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=87r48f4io8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.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).