public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix bogus function cast warning for functions with common arg subset
Date: Fri, 23 Feb 2018 15:50:00 -0000	[thread overview]
Message-ID: <1519401043.2913.34.camel@redhat.com> (raw)
In-Reply-To: <20180223034045.26231-1-siddhesh@sourceware.org>

On Fri, 2018-02-23 at 09:10 +0530, Siddhesh Poyarekar wrote:
> Libraries like gtk/glib[1] and python[2] use functions with common
> argument subsets to register callbacks.  The working idea behind it
> is
> to have a flag in the structure (or some other pre-determined method)
> that specifies how the callback is cast and called.
> 
> Fix this by not throwing a warning when functions with different
> argument list lengths (of M and N where M < N) have compatible
> argument types for the first M arguments.

Do we have a PR open for this yet?

I believe this is an example of where this bit (for the Python case):
  https://github.com/imageworks/OpenColorIO/pull/518

[...snip...]


Dave

  reply	other threads:[~2018-02-23 15:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23  3:40 Siddhesh Poyarekar
2018-02-23 15:50 ` David Malcolm [this message]
2018-02-23 16:12   ` Siddhesh Poyarekar
2018-02-23 18:31     ` Richard Biener
2018-02-23 18:52       ` Siddhesh Poyarekar
2018-02-23 20:02         ` Martin Sebor
2018-02-23 20:32           ` Siddhesh Poyarekar
2018-02-23 21:58             ` Martin Sebor
2018-02-26  6:55               ` Siddhesh Poyarekar

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=1519401043.2913.34.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=siddhesh@sourceware.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).