Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [RFC] LONGEST and ULONGEST function template instantiation
Date: Wed, 14 Jun 2017 13:54:00 -0000	[thread overview]
Message-ID: <4128F440-F798-4BA5-BEFC-4008D3F65BE0@arm.com> (raw)
In-Reply-To: <CAH=s-PPP7v1QTSD7Tg-DbVHWr0Egp18KN4XWu=CjTBBMDO9dOg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 918 bytes --]


> On 13 Jun 2017, at 12:33, Yao Qi <qiyaoltc@gmail.com> wrote:
> 
> On Tue, Jun 13, 2017 at 12:29 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
> 
>> 
>> This patch was posted here
>> https://sourceware.org/ml/gdb-patches/2017-05/msg00492.html but the
>> problem was fixed in a different way.  However, I think the patch is still
>> useful to shorten the code.
> 
> Add Alan to CC.
> 

> It is an RFC, because I am not sure people like it or hate it :)

My only objection to this would be that “enable_if” is fairly confusing.
However, having said that, I think the end result is quite nice, and
calling the functions is very simple, so I withdraw my objection.

It would be nice if the header files could use “LongType” instead of
the longer “enable_if” block, however I remember when I tried this
myself and couldn’t find a way around it.


Alan.

\x16º&Öéj×!zÊÞ¶êç×\x7f|Óyb²Ö«r\x18\x1dn–­r\x17¬

  reply	other threads:[~2017-06-14 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 11:29 Yao Qi
2017-06-13 11:33 ` Yao Qi
2017-06-14 13:54   ` Alan Hayward [this message]
2017-06-14 16:12 ` Pedro Alves
2017-06-15 11:59   ` Yao Qi
2017-06-15 16:19     ` Pedro Alves
2017-06-16 14:46       ` 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=4128F440-F798-4BA5-BEFC-4008D3F65BE0@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=qiyaoltc@gmail.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