[FFmpeg-devel] [PATCH] doc/ffmpeg: do not show examples making use of the deprecated glob_sequence pattern type

Stefano Sabatini stefasab at gmail.com
Wed Aug 8 10:04:04 CEST 2012

On date Wednesday 2012-08-08 00:49:05 +0200, Alexander Strasser encoded:
> Hi Stefano,
> Stefano Sabatini wrote:
> > The syntax of the 'glob_sequence' pattern type is explained in the image2
> > manual section, so there is no need to replicate it here.
> > 
> > Also discourage the use of such deprecated pattern type by not showing
> > examples employing it.
> > 
> > Replace the syntax explanation with an use example of the 'glob' pattern
> > type.
> > ---
> >  doc/ffmpeg.texi |   20 +++++++++-----------
> [...]
> > +When importing an image sequence, -i also supports expanding
> > +shell-like wildcard patterns (globbing) internally, by selecting the
> > +private image2 @code{-pattern_type glob} option.
> IMHO "image2-specific @code{-pattern_type glob} option" is more
> understandable for end users.

Fixed locally.
> Not related to this patch: 
>   Also I conclude that codec-private, private codec, or
> private <other component> option is a misnomer! If it were
> private according to the common meaning of private in the
> programming/software development/computer science/informatik
> field then it would be a violation of the principle to
> access those options from outside of the module itself.

Given this definition:

           These options are specific to the given container, device
           or codec. Private options are listed under their
           corresponding containers/devices/codecs.

I agree the term "specific" would have been more appropriate. On the
other hand, "private" is intended in this context as denoting
an option "not belonging to the public namespace", and the
antonym of "public" is "private".
FFmpeg = Fundamentalist Fantastic Mysterious Philosofic Excellent Geek

More information about the ffmpeg-devel mailing list