Branko Čibej wrote:
> Gregg Tavares wrote:
>
>> Are there already plans to add it to all the other commands? Or, if
>> not, does anyone mind if I add it and send in the patches?
>
> I would certainly like to see the --xml flag supported in all commands
> that produce output. [...]
I had only thought of XML output for commands whose primary purpose is to
produce output.
I have never seriously considered producing XML output for error, warning and
progress messages.
>> For exmaple, I'm using "svn lock <file>". If the file is locked it
>> returns something like
>>
>> 'file:folder\file.c' is already checked out by user 'gregg' in
>> 'http://svn.domain.com/project/folder/file.c'
>>
>> Unfortunately
>>
>> 1) all that changes if you are not running in English Windows so you
>> can't parse by word
>> 2) filenames can have single quotes in them so trying to parse by
>> single quotes won't work either.
OK. But I don't think XML is a good mechanism for outputting error, warning or
progress messages.
I think if you are writing a higher-level program or wrapper that uses
Subversion, and is complex enough that it needs to parse error messages rather
than just report them to the user and exit, then you would be better off using
one of the other ways of interfacing. As well as calling the Subversion
library functions from C, we also have language bindings so that you can call
them from Python, Java, and various other languages.
If you would like to explain what you are doing with Subversion, we might be
able to suggest the best course of action.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 27 19:46:02 2005