If you're not opposed to using (if only as a shim layer) the C programming
language, may I (and presumably "we", with Daniel in mind) suggest that you
use Subversion's existing parser API (svn_repos_parse_dumpstream2) and
simply supply your own customized parser callback function vtable?
On 04/16/
I'm writing a svndumpfilter-like tool and I want to make sure it can handle
anything svn can produce.
On Apr 16, 2013 4:08 PM, "Daniel Shahaf" wrote:
> Eitan Mosenkis wrote on Tue, Apr 16, 2013 at 12:22:00 -0400:
> > This would make it easier for implementers to write accurate parsers.
>
> Why ar
Eitan Mosenkis wrote on Tue, Apr 16, 2013 at 12:22:00 -0400:
> This would make it easier for implementers to write accurate parsers.
Why are you re-implementing the parser?
The documentation for dump files (
http://svn.apache.org/repos/asf/subversion/trunk/notes/dump-load-format.txt)
states that headers are RFC822-style. RFC822 describes several complex
behaviors for headers that are not used (and probably not supported) by
SVN. Perhaps the reference to RFC822 could
