On Thu, Jun 11, 2009 at 10:21:06AM -0400, C. Michael Pilato wrote:
> Do we not having a single function that can take a array of const char *,
> native encoding path-spec arguments and return an array of structures that
> contain a UTF-8 const char * path field and peg revision? Seems like we
> could stand to have such a thing if we don't already. We could then have
> helper functions that accept one of those structures and do other
> transformations on it, such as expanding shortcut URLs (^/) and IRIs
> ("http://server/path with spaces") into canonical form, and so on.
> I dunno ... I guess I just figured that after 9 years, we'd know how to
> consistently parse our command-line arguments.
Yes, I agree that this is necessary.
I have opened a new bite-sized issue:
I've just committed my patch in r37988 (which probably triggered your
response), and I still think it is useful because it should be far easier
to backport to 1.6 than what you are describing. There are two minor
tree conflicts, that's all. I'll create a backport branch in a minute.
Received on 2009-06-11 17:11:06 CEST