[vlc-devel] vlc: svn commit r25242 (damienf)
damien.fouilleul at laposte.net
Thu Feb 21 16:12:37 CET 2008
I already use --plugin-path to pass the plugin path from the registry
setting, argv allows a user to override that path and provides more
flexibility for deploying VLC.
I didn't design this. Since day 1, vlc leverages that feature as the
path in argv is added to the plugin search path. removing this is a
mistake, as you may break shell scripts, etc...
this can be easily hidden away in bindings.
there are way bigger hacks in POSIX than this, take errno, for
On 21 Feb 2008, at 14:51, Olivier Aubert wrote:
>> libvlc: document that libvlc_new() MUST have a program path in
>> From my point of view, using argv to deduce module paths is a lame
> hack, and should be removed in favor of an explicit way of setting
> (for instance, the --plugin-path option already allows to pass a
> directory to search for plugins).
> An API is intended to provide some level of abstraction over its
> internal mechanism. The argv is an internal mechanism, which should
> be abstracted.
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
More information about the vlc-devel