[FFmpeg-devel] [PATCH] [2/??] [3/3] Filter graphs - Parser for a graph description
Wed Mar 19 17:38:29 CET 2008
On Wed, Mar 19, 2008 at 03:42:39PM +0000, vmrsss wrote:
> (*) this should be clear from what I wrote previously, just in case
> I'll repeat it: the problem is that you cannot put together two
> previously defined graphs which happen to use a common name for their
> input pads, because you'll get confused as to which is which. You can
> of course modify one of the graphs by hands, don't think is
> particularly user friendly, then you'll have to provide a programmatic
> way to do so. It can be done of course, but it's not pretty, and it's
> not easy to explain to end users.
Ive provided a formal proof of equivalency already. You are trying to
tell me that you dont understand math ? Because if you did you wouldnt
argue against a proof ...
Non formally i could again point you to C and say that it doesnt matter what
arguments to a function are named nor what local variable names are used
in a function. You do NOT solve anything by ommiting names, its just that
you then have no names. Which will negativly affect readability.
a system with names:
(main, left, right, bot)my_overlay=
use of it is the same either way:
*movie=bottom.avi , my_overlay
And yes a system without names is surely shorter, and so would be C if one
ommited variable names and used rules to implicitly select them. This doesnt
make it a good idea though.
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When the tyrant has disposed of foreign enemies by conquest or treaty, and
there is nothing more to fear from them, then he is always stirring up
some war or other, in order that the people may require a leader. -- Plato
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel