Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fftools/objpool: Don't use return with expression when returning void
Date: Sat, 23 Jul 2022 18:51:12 +0200
Message-ID: <CA+anqdz3=95FyPXMDHYBXkb4dUgS7u4OLecu5pM2JaktMpG09g@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0101MB22149A96B17C439FB86A651B8F939@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com>

On Sat, Jul 23, 2022 at 6:24 PM Andreas Rheinhardt
<andreas.rheinhardt@outlook.com> wrote:
>
> Using tail calls with functions returning void is forbidden
> (C99/C11 6.8.6.4: "A return statement with an expression shall not appear
> in a function whose return type is void.") GCC emits a warning
> because of this when using -pedantic: "ISO C forbids ‘return’ with
> expression, in function returning void"
>
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
>  fftools/objpool.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fftools/objpool.c b/fftools/objpool.c
> index b1561ecd69..06e4f069a5 100644
> --- a/fftools/objpool.c
> +++ b/fftools/objpool.c
> @@ -101,11 +101,13 @@ static void *alloc_frame(void)
>
>  static void reset_packet(void *obj)
>  {
> -    return av_packet_unref(obj);
> +    av_packet_unref(obj);
> +    return;
>  }
>  static void reset_frame(void *obj)
>  {
> -    return av_frame_unref(obj);
> +    av_frame_unref(obj);
> +    return;
>  }
>

Maybe leave out the return's entirely? Its not a pattern we typically
use to have return at the end of a function.

- Hendrik
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-07-23 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 16:24 Andreas Rheinhardt
2022-07-23 16:51 ` Hendrik Leppkes [this message]
2022-07-23 16:53   ` Andreas Rheinhardt

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='CA+anqdz3=95FyPXMDHYBXkb4dUgS7u4OLecu5pM2JaktMpG09g@mail.gmail.com' \
    --to=h.leppkes@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git