[vlc-devel] vlc: svn commit r25242 (damienf)
damien.fouilleul at laposte.net
Thu Feb 21 22:56:44 CET 2008
For once in your life, please give me a practical answer to what we
really have to gain by removing argv and please leave off dogmatic
theories about being right or wrong.
I only see advantages, the only constructive counter argument I got so
far is that it could confuse users which I believe can be fixed with
proper documentation (if anything, it keeps the construct similar to
main(), which should be less confusing by the way)
by providing a user configurable argv, a user can put a fully
qualified pathname, which is pre-prepended to modules search paths, as
it was done previously. Moreover, language bindings can also put a
meaningful names such as "python" or "java", which can only improve
On 21 Feb 2008, at 18:12, Rémi Denis-Courmont wrote:
> Le Thursday 21 February 2008 19:38:21 Damien Fouilleul, vous avez
> écrit :
>> you obviously don't read the forums very often. i've leveraged the
>> of argv as per request from multiple users from the user who
>> to be able to bundle mozilla and activex and their plugins easily.
> Yeah, and you obviously don't try to run the installed (stable) vlc
> from a
> parent directory of vlc development tree. Because this breaks it.
> Not talking
> about the speed issue.
> That a user asks for something does not automatically mean it's a
> good idea.
>>> Since when are software libraries suppose to use argv anyway?
>>> I've not
>>> bothered to remove it from the whole internal LibVLC command line
>>> flow, perhaps. That surely did not mean we intended to restore the
>>> misfeature later on.
>> this comment is about as interesting as saying since when chickens
>> have teeth.
> Perhaps. It was your argument anyway.
> Rémi Denis-Courmont
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
More information about the vlc-devel