Julian Foad wrote:
> D.J. Heap wrote:
>
>>
>> The rest of this issue involves error messages. There are hundreds I
>> have found so far that use internal style paths, and in several cases
>> the path could be a url -- no distinction is made, so a url check would
>> need to be made before calling the conversion function, before passing
>> the path to the error creation function. Should I proceed with this?
>> Any comments or recommendations?
>
>
[snip]
> Don't add special code to every place that generates such an error
> message. Use a single common function to convert a path to a form
> suitable for display. There are several potential things to do to a
> path in an error message:
> This formatting function could, if people wish, be configurable: e.g. if
> absolute paths are unwieldy in most cases, it could print relative paths
> by default and only when someone is stuck not knowing where to look they
> could re-try the operation with a configuration option (debug level) set
> to display absolute paths.
[snip]
Thanks for the comments and patch, Brane, Julian and Philip. I will
start in on this but it will likely take a while.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 26 18:29:33 2003