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

Re: Sanity check: removing src_err

From: Glenn A. Thompson <gthompson_at_cdr.net>
Date: 2002-12-10 09:03:47 CET

Hmmm,

A thought; how about having a SVN_EXTERNAL error code. So, a program
could traverse the errors looking for SVN_EXTERNA if it needs to get at
it later. This would allow me to put anything I want in there. Chars too!
When you want to keep a src err simply create a SVN_EXTERNAL wrapped by
whatever the SVN_MAPPING would be?
So I could create a error like "ORA-0001". Or "MySql-0001". I guess I
can do this anyway. But it seems nice to identify certain errors as
"from external sources".

gat

Greg Hudson wrote:

>On Tue, 2002-12-10 at 01:32, Glenn A. Thompson wrote:
>
>
>>Hey,
>>How do you plan on detecting DEADLOCK Errors?
>>
>>
>
>Probably the easiest way is a dedicated svn_fs error code for deadlocks.
>
>As to why I dislike src_err: it is an extra argument to every
>svn_error_create call for the sake of a vanishingly small number of
>cases, its value lives in an indeterminate number space, and it renders
>the use of the error system prone to confusing inconsistencies.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 09:02:40 2002

This is an archived mail posted to the Subversion Dev mailing list.