RE: --xml on all svn commands

One language that does not have suitable bindings is Visual Basic / VBScript for use in WSH scripts. We do, however, have a class that will let us call a command line and collect the output in a string variable. XML output would give us something we could actually use without a big headache.

Specifically, I have often longed for XML output for the "update" and "switch" subcommands so that my VBScript can easily parse the list of changed files and construct an update patch (including applying database changes) to reflect the delta.

My opinion: Go for it, Gregg!!

[Too bad I'm too busy (lazy?) to write the patches myself...]

S_E_D

-----Original Message-----
From: Julian Foad [mailto:julianfoad@btopenworld.com]
Sent: Tuesday, September 27, 2005 12:45 PM
To: Branko Èibej; Gregg Tavares
Cc: dev@subversion.tigris.org
Subject: Re: --xml on all svn commands

[snip]

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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 27 20:29:26 2005