Re: [PATCH]Can we accept JavaHL Revison.Number.Number(-1)?

Mark Phippard wrote:
> Maybe the underlying native API you want to call supports this
> functionality and there are internal cases where it is used or needed,
> but before we expose this to users via JavaHL I think we should
> understand why we would want to. I notice the native API is a double
> underscore, so maybe that is a good sign that it is not correct to
> expose this as is. Why not just have an API like this that is
> exposed?
>
> /**
> * Returns the youngest revision number for path.
> * @since 1.6
> */
> public native long getYoungestRevisionNumber(String pathOrUrl);
>
> Internally, this could call the native API and hide the other details.

It would still need to call a public libsvn_client API, since the C++
layer of the JavaHL bindings only has access to public APIs.

-Hyrum