[vlc-devel] vlc: svn commit r25242 (damienf)

Damien Fouilleul 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[0] 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[0] 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  
example ;)


On 21 Feb 2008, at 14:51, Olivier Aubert wrote:

>> libvlc: document that libvlc_new() MUST have a program path in  
>> argv[0]
>> From my point of view, using argv[0] to deduce module paths is a lame
> hack, and should be removed in favor of an explicit way of setting  
> this
> (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[0] is an internal mechanism, which should
> be abstracted.
> Olivier
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> http://mailman.videolan.org/listinfo/vlc-devel

More information about the vlc-devel mailing list