Re: [FFmpeg-devel] State of decklink_ctx vs. decklink_cctx

2018-03-27 Thread Devin Heitmueller
Hi Grady, > On Mar 27, 2018, at 3:05 PM, grady player wrote: > > So I haven't looked in great detail so this may all be info that you know, > and maybe not helpful... > > 1. You can easily link C objects to C++ code by marking it `extern "C"` > 2. You can not easily link C++ objects to C code,

Re: [FFmpeg-devel] State of decklink_ctx vs. decklink_cctx

2018-03-27 Thread grady player
So I haven't looked in great detail so this may all be info that you know, and maybe not helpful... 1. You can easily link C objects to C++ code by marking it `extern "C"` 2. You can not easily link C++ objects to C code, because there are classes, vtables, name mangling etc. 3. The solution for

[FFmpeg-devel] State of decklink_ctx vs. decklink_cctx

2018-03-27 Thread Devin Heitmueller
Hello, I’m continuing to do some cleanup work on the decklink libavdevice input/output, and I’m trying to understand how the way state is managed has evolved over time. Specifically, there are two key state structures - decklink_ctx and decklink_cctx. It would appear the motivation behind thi