Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Make implicit void pointer cast explicit
Date: Tue, 19 Jul 2022 23:23:56 +0200
Message-ID: <Ytcg7EXuSjNxd2XR@phare.normalesup.org> (raw)
In-Reply-To: <CAMMoCOf5oawGbi4DPyyFeXOtS_-K3xcAXX7zjG34FSyz8G95+A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]

Amir Mazzarella (12022-07-19):
> Thank you for your response! A C++ compiler can't do implicit casts like a
> C compiler can, in this instance. This is fine for most of FFmpeg's
> codebase, since these tricks are in C source files, but in this instance it
> is in a header file. If any C++ code includes this header file, even with
> extern "C", it won't be able to be compiled.

Thanks for clarifying. I confess I had more or less guessed. FFmpeg is
C, and its headers, public or not, as a rule do not contain
accommodations to be included as is in other languages.

> On Tue, Jul 19, 2022 at 12:08 PM Nicolas George <george@nsup.org> wrote:

Please remember that top-posting is forbidden on this mailing-list. If
you do not know what it means, look it up.

Regards,

-- 
  Nicolas George

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  parent reply	other threads:[~2022-07-19 21:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09  4:31 Amir Mazzarella
2022-07-19 18:32 ` Amir Mazzarella
2022-07-19 19:08 ` Nicolas George
2022-07-19 21:21   ` Amir Mazzarella
2022-07-19 21:23     ` Hendrik Leppkes
2022-07-19 21:23     ` Nicolas George [this message]
2022-07-19 22:12       ` Amir Mazzarella
2022-07-20  9:01         ` Nicolas George
2022-07-28 14:11     ` Anton Khirnov

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=Ytcg7EXuSjNxd2XR@phare.normalesup.org \
    --to=george@nsup.org \
    --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