From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 12 Apr 2013 18:57:58 +0100 (BST)
Daniel Shahaf wrote:
> Prompted by Julian's review of this freshly-minted public API on IRC:
I'm not sure that's necessarily an improvement. We recently decided to show the E155019 code to help users search. Now
> 3. Should the API return the error code, or the error code without the
I'm not a fan of verbosity, so I think it's reasonable to leave off the prefix in the svn smdline err msgs if we do display it. Users (and developers) will sometimes leave the prefix out when writing casually, anyway, even if it was displayed.
The API, on the other hand, should do whatever works best as an API. We're intentionally leaving open the possibility of extending it to translate err codes that are returned by Subversion but originate from some other software layer, such as the E000002 codes in the example above. It seems messy to stript the prefix from SVN_ERR_ if we'll also be returning non-svn err codes (and haven't decided whether we'll try to strip some prefixes from them too). But whether the API returns the prefix or not has very little bearing on the success of users searching on the net -- that is a whole two or three social and technical levels away from the API design.
> I also attached a patch which implements (2), in case we want it.
This is an archived mail posted to the Subversion Dev mailing list.