const_name -> const_names
const_value -> const_values
func[12]_name -> func[12]_names
func[12] -> funcs[12]
All these parameters contain a list of values, using plural names for
them help understanding a little.
Originally committed as revision 23403 to svn://svn.ffmpeg.org/ffmpeg/trunk
containing an error code.
Allow these functions to convey the reason of the failure to the
calling function, failure which is not always due to a parsing error
but it may depend for example on a memory problem.
Also fix several potential memleaks.
Originally committed as revision 23402 to svn://svn.ffmpeg.org/ffmpeg/trunk
ff_parse_and_eval_expr(), place the names for constants/functions
before the corresponding values.
This looks more readable, as the user is expected to know the names
before the values.
Originally committed as revision 23149 to svn://svn.ffmpeg.org/ffmpeg/trunk
Passing an explicit filename to this command is only necessary if the
documentation in the @file block refers to a file different from the
one the block resides in.
Originally committed as revision 22921 to svn://svn.ffmpeg.org/ffmpeg/trunk
ff_parse_and_eval_expr().
Change func[12] attributes from "** func" to "* const * func".
This is consistent with the semantics of the provided arrays of
functions, which are not supposed to be changed by the ff_parse_*
functions.
Also fix the GCC compilation warnings:
libavcodec/ratecontrol.c: In function ‘ff_rate_control_init’:
libavcodec/ratecontrol.c:109: warning: passing argument 3 of ‘ff_parse_expr’ discards qualifiers from pointer target type
libavcodec/eval.h:69: note: expected ‘double (**)(void *, double)’ but argument is of type ‘double (* const*)(void *, double)’
Originally committed as revision 22860 to svn://svn.ffmpeg.org/ffmpeg/trunk
ff_parse_and_eval_expr().
Change attribute from "const char **" to "const char * const *".
The name arrays are not supposed to be changed by the function.
Originally committed as revision 22859 to svn://svn.ffmpeg.org/ffmpeg/trunk
The new name is more expressive and fits better in the overall naming
scheme for the revisited eval API.
Originally committed as revision 22858 to svn://svn.ffmpeg.org/ffmpeg/trunk
This way we have to deal only with struct AVExpr and AVExpr, which is
slightly less confusing as the association between the two symbols is
obvious.
Originally committed as revision 22839 to svn://svn.ffmpeg.org/ffmpeg/trunk
There is a theoretical possibility to pass a very long string to ff_parse,
which could crash if allocated from the stack. This allows the allocation
to be checked properly.
Originally committed as revision 19670 to svn://svn.ffmpeg.org/ffmpeg/trunk
Otherwise doxygen complains about ambiguous filenames when files exist
under the same name in different subdirectories.
Originally committed as revision 16912 to svn://svn.ffmpeg.org/ffmpeg/trunk
utils.c: In function ‘avcodec_get_context_defaults2’:
utils.c:793: warning: assignment discards qualifiers from pointer target type
Originally committed as revision 11938 to svn://svn.ffmpeg.org/ffmpeg/trunk
eval.c:454: warning: return type defaults to 'int'
eval.c:464: warning: control reaches end of non-void function
Originally committed as revision 11594 to svn://svn.ffmpeg.org/ffmpeg/trunk
support variables, the syntax isnt beautifull (st(a,b) means var[a]=b and ld(a) var[a]) but for a mere 19 lines of code its fairly simple, if anyone wants to write real variables support with names for variables and = and [] then that would of course be welcome but only if it doesnt bloat the code up terribly...)
Originally committed as revision 6813 to svn://svn.ffmpeg.org/ffmpeg/trunk
Stefano Sabatini
Michael Niedermayer
Diego Biurrun
Ramiro Polla
Måns Rullgård
Anders Grönberg
Stefan Gehrer
Aurelien Jacobs
Luca Abeni
Reimar Döffinger
Luca Barbato
Oded Shimon