On Mon, 2002-10-28 at 18:57, Branko Èibej wrote:
> How do you propose to wrap svn_error_creatf without using C99 varargs
> macros? I don't see how it's possible short of explicitly passing
> __FILE__ and __LINE__ to every svn_error_createf call.
Oh, I hadn't thought about that. Fooey.
I don't suppose people would go for having to write
svn_error_createf(apr_err, src_err, child, (fmt, args)), either.
> > * We should always collect line and file information, but only
> > expose it with the appropriate flag set. This will help with
> > debugging and will simplify the internal interface.
> No, we should _collect_ it only with the appropriate flag set
Why?
From a separate message:
> I'm sick and tired of how our Python test harness depends on "svn
> import" working correctly.
I don't see how this is a serious problem. But perhaps relying on
"svnadmin load" would be a good compromise. That way the test harness
wouldn't rely on as much Subversion machinery working, but the same
input data would work for any filesystem back end.
My quibble about the test harness is that when a cmdline test fails, I
can't easily bring up the same command in a debugger to find out what
went wrong. I'd like it if tests.log contained a log of commands run so
I can find out which command failed. Plus, if a command seg faults, I'd
like a note to that effect; as it stands, I get an unexplained "FAIL:"
and I have to notice the core file lying around.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 29 01:59:55 2002