[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: parsing of svn CLI by other programs

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-10-16 16:44:36 CEST

john smallberries <jackdied@yahoo.com> writes:
> .. but there will inenvitably be front ends that rely
> on text I/O(I'm sure the emacs front end will) from
> the standard svn CLI. Is there a proper place to
> store the knowledge of what these messages look like
> (comments, resource files)? do you just let the guy
> who writes the parser deal with it or do you go out of
> your way to format all messages in a parsable (BNF)
> way?

If we're good, we'll eventually write a formal specification about
what the output formats look like. But the UI and outputs are still
changing and being refined, because we've not yet hit Alpha. I
wouldn't assume things are "safe" until we reach that point.

(On the other hand, right now our python regression tests are *very*
dependent on parsing CLI output. That fact alone keeps us from
changing the formats too much!)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.