1. I only plan to make this change for RA API. The change to existing code
is a different question and I think it should be left alone because of
backwards compatibility.
2. Code can still catch the runtime exception derived from
SubversionRuntimeException just like it does with the checked except
On Tue, May 29, 2012 at 8:32 PM, Blair Zajac wrote:
> On 05/21/2012 04:18 AM, Vladimir Berezniker wrote:
>>
>> Hyrum,
>>
>> 4. Use runtime rather than checked exceptions.
>>
>> I strongly dislike checked exceptions in code paths where there is
>> no expected recovery logic that can be applied.
To be clear, for now I am only proposing this for the new RA APIs. I would
keep existing SVNClient and SVNRepos as is, because of backwards
compatibility. However, given large amount of shared code this might not be
practical.
Yes, I propose that checked exceptions would be used in cases when clie
On 05/21/2012 04:18 AM, Vladimir Berezniker wrote:
Hyrum,
4. Use runtime rather than checked exceptions.
I strongly dislike checked exceptions in code paths where there is
no expected recovery logic that can be applied. This just forces people
to either write a lot of try catch blocks that
Hyrum,
I was thinking of adding, what I have implemented so far, on top of the
existing branch as there is minimal overlap and I would like to incorporate
the existing work. Therefore, my plan is to do the following,
not necessarily in the below order:
1. Rename SVNReposNaming to SVNRa.
I h
Vladimir,
Feel free to delete the existing branch and start a new one for your
work. Your patches look to be much more complete than what exists on
the branch now.
-Hyrum
On Fri, May 18, 2012 at 4:12 PM, wrote:
> Author: vmpn
> Date: Fri May 18 21:12:26 2012
> New Revision: 1340253
>
> URL: ht
6 matches
Mail list logo
