"Bert Huijben" <b...@qqmail.nl> writes: > Unless there are a lot of string creations to create a vey specific > error message, I've never seen a construction of svn_error_t * in any > performance traces...
It is possible: in 2003 I comitted r847626 to avoid an svn_error_t overhead in the working-copy access-baton code. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
