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

Re: bad output format design issue: svn log -v format is not parseable :-(

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-04-05 18:15:20 CEST

Marc Haisenko wrote:

> On Monday 05 April 2004 14:54, kfogel@collab.net wrote:
>>Saying this output is "not parseable" or "evil" is a bit strong :-).
>>The output is, in a very rare edge case, ambiguous. If you create
>>files whose names end in " (from ...)", you will have a problem, yes.
>>Sorry for that -- perhaps we should have been better about escaping.
>>Nevertheless, *do* you actually create such files? If not, the output
>>is quite easy to parse.
> But someone might do so sometime, and the universe likes to produce people
> that do just these things from which other people think "this won't happen,
> or happen rarily" ;-) It's always the same... and a filename ".*(from.*)" is
> not all that unlikely.
> In the normal command line output I can't think of an alternative as this
> format also has the advantage of being easily parsed with a regexp, although
> you can run into a bug if your regexp is not built carefully enough. But in
> the XML output you could surely make this a tag property pretty easily, no ?

If you follow the thread I tried XML and ended with a new problem,
the "#13\r\n" linefeeds inside of the log messages.
I also think using an XML parser for this task is overkill.
I'd get a new deopendency on an XML parser module in my tools,
have to find a free or at least LGPL parser that is bugfree and
up-to-date etc...
maybe my simple "TAB" patch will do.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 5 18:15:22 2004

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.