Re: Which family of path/dirent/uri/relpath functions to use for svn_lock_t->path?

[Julian Foad]
> Proposal for switching to a dedicated "fs path" API:
>
> Step 1: Introduce a new API for FS paths, as a thin layer that maps to
> existing path APIs. It must assert that the fspath arguments and fspath
> return values begin with '/'. Initially it should map directly to
> svn_uri_*, so that it can be seen to be a direct replacement.

So do these or do these not involve doing URI escaping? %20 for space,
etc. By calling them 'fs paths', the assumption is that these are in
UTF-8, and there is no marshalling / escaping to even think about,
except when converting it to or from a URI or dirent. Is that the
intent?

> Bikeshed: svn_fspath__* or svn_fs__path_* or something else?

svn_fspath__ seems better to me. svn_fs__path_ sounds like this is all
internal to libsvn_fs, whereas I understand you want this in
libsvn_subr for layers to use that are _not_ specifically talking about
svn_fs internals.

-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/