Bert Huijben wrote on Sun, May 12, 2013 at 22:48:37 +0200: > In this specific case I'm pretty sure that the error will actually > just go to the user, but in general I would be -0.5 on performing this > kind of escapes in the creation of error messages that are part of our > libraries that are also used by GUIs and bindings that might want to > apply different handling and see the raw values.
Are you suggesting we need to support a way to _parse_ the path out of the error message? If so, perhaps we should add a 'const char *extra[];' member to struct svn_error_t. If we extend svn_error_t we might also look into supporting >1 children, to facilitate svn_error_compose_create(); compare Python's "raise from". Daniel (based on a conversation I had with Mattias yesterday)
