Karl Fogel wrote:
>Greg Hudson <ghudson@MIT.EDU> writes:
>
>
>> svn_error: #21079 : <Item already exists in filesystem>
>> file `file:///var/ghudson/svn-test/grows' already exists.
>>
>>Aside from being visually ugly with the leading newline, an unschooled
>>reader is likely to get caught up in the cryptic "svn_error: #21044 : <
>>...>" and take more time to get to the important text. I would display
>>this as, perhaps:
>>
>> svn: Item already exists in filesystem
>> svn: file `file:///var/ghudson/svn-test/grows' already exists.
>>
>>
>
>+1 all *over* that.
>
>The error codes don't even help developers, since we don't know them
>numerically, we know them by error constant. We should print out the
>constant's source name if we can, or just not print a code at all.
>The raw codes alarm users while helping no one.
>
FYI, I'm taking this on. Have to do something while trying to grok what
Greg Stein wrote in gen_base.py...
(Ah, the good old times are back, qualifying Gregs has become necessary
again. :-)
>Also agree that the solution to cryptic errors is to write better
>error strings (both for the core error string and/or for the
>call-specific string where the error was created).
>
>
That, of course, means first deciding on a policy, documenting it, then
going through the code and implementing it. I'll wisely avoid this issue
for now. :-)
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 22:04:52 2002