[FFmpeg-devel] [RFC] eval API review

Stefano Sabatini stefano.sabatini-lala
Fri Apr 2 18:32:31 CEST 2010

Hi all,

it has been mentioned many times that the eval API should be moved
from lavc to lavu and make it public, where it could be used by
non-lavc dependant applications and libraries (e.g. libswscale and

Michael also mentioned that he wanted to review the API before to make
it public, follows an attempt at it.

Main differences with respect to the current internal API regards the
fact that in the proposed API the functions don't set a string in case
of error, but use a return error code to convey if the operation
performed was successfull, while the explanation of the error
condition is supposed to be logged using av_log_*.

Note the suffix "2" in av_strtod2(), this is required as we already
have an av_ prefixed av_strtod() function in the public API, the new
av_strtod2() is consistent with the previously described interface

My plan is to move the code from lavu to lavc, while retaining in lavc
a backward compatibility layer, which will be dropped at the next lavc
major bump.

Comments are welcome, regards.
FFmpeg = Fabulous and Fiendish Merciless Programmable Explosive Gnome
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eval.h
Type: text/x-chdr
Size: 5319 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20100402/84056a7f/attachment.h>

More information about the ffmpeg-devel mailing list