On 8/1/06, david reid <[EMAIL PROTECTED]> wrote:
Having looked at these, they're small and self contained and would seem to be a good fit for apr-util. Question is where/how would they go in? The functionality revolves around uri's, but I'm not sure the existing apr_uri_ stuff is a sensible match...
I'd still call it apr_uri_encode and apr_uri_decode. There's no need to confuse downstream developers - let's just be honest about what it does. Anything else overcomplicates it. -- justin
