On 1/2/2019 4:43 PM, Michael Niedermayer wrote:
On Wed, Jan 02, 2019 at 10:34:21AM -0900, Lou Logan wrote:
On Mon, Dec 31, 2018, at 12:03 PM, Michael Niedermayer wrote:
Signed-off-by: Michael Niedermayer <mich...@niedermayer.cc>
---
  doc/indevs.texi | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
Ok.  Same typo is in compat/avisynth/avisynth_c.h.
yes, you should probably report this to avisynth or whereever this is 
maintained if the
typo is still in the upstream version, otherwise our copy should maybe be 
updated
For statistics' sake, the commit introducing that text was from November 2014¹, and it happened on the original 2.6 CVS on Sourceforge (which no longer provides CVS, and 2.6 hasn't migrated to SVN or Git on Sourceforge; the inactivity is generally assumed to mean AviSynth+ should be treated as 'upstream').

AviSynth+ merged in those changes sometime later, and are still present in the current/de facto development HEAD².  The version we ship in compat is slightly older than what AviSynth+ currently provides, due to some issues with MSVC/GCC client program compatibility in the avs/capi.h header when [the chronically fragile support for] GCC compilation of the main AviSynth+ project was added in 2016.

¹a mirror of the CVS version of the file from 2015: https://github.com/jeeb/avisynth/blame/master/src/core/avisynth_c.h
²https://github.com/pinterf/AviSynthPlus/blob/MT/avs_core/include/avisynth_c.h#L255

tl;dr: the header shipped in compat isn't really out of date with upstream in its essential functions,
so if the typo just gets fixed here it's probably not a big deal.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to