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

Re: [PATCH] include error codes in error messages

From: Branko Čibej <brane_at_xbc.nu>
Date: Thu, 07 Feb 2008 14:15:41 +0100

C. Michael Pilato wrote:
> David Glasser wrote:
>> On Feb 6, 2008 1:23 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>>> Branko Čibej wrote:
>>>> Another thing that strikes me is that the whole errror number, e.g.
>>>> 200011 in the example above, is quite and completely useless; because
>>>> you never *see* that number in the code! You see some constant +
>>>> 11, so
>>>> this display is quite useless for searching for the cause.
>>> That's what tools/dev/which-error.py is for!
>>>
>>> $ tools/dev/which-error.py 200011
>>> 00200011 SVN_ERR_DIR_NOT_EMPTY
>>> $
>>
>> And if we're actually shipping user-visible error codes, I'd be up for
>> whipping together a little webapp running somewhere that does the same
>> mapping.
>
> Is APR's base error programmatically set, though? I always assumed it
> was, which would make our error codes build-specific. Of course, if
> that was true, we'd have a booger of a time trying to get good error
> codes from our remote servers, wouldn't we? So, maybe that's a
> non-issue.

It's a compile-time constant. I've never seen it change from the days of
0.x.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-07 14:15:59 CET

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.