Re: Bug: IP address bogusly interpreted as peg revision

Julian Foad <julianfoad_at_btopenworld.com> writes:
> It sounds to me like what's broken is the idea that we can validly stick the
> "@PEG" back on to a path or URL again after parsing and canonicalising it.
>
> Do you think we can get rid of all the code that relies on that, and
> deprecate the functions that do it and any functions that currently
> take "<canonical path or URL>@PEG" as input? Once we've parsed the
> syntax, keep the results separate. That sounds like the Right
> Thing. (The alternative, if we insist on glueing the two parts back
> together, is to define how we're going to do it in a way that doesn't
> lose information.)

Public APIs would still take

   <canonical path or URL>@PEG

right? Then we have the problem of one public API calling another one.

Or are you proposing that users of our APIs would call some public
function to separate THING[@PEG] into a { THING, [PEG] } structure,
and then all the other public APIs would take that structure?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-28 17:41:13 CEST