| commit | 55402474f92d9de741be2b0587587f206a4272cf | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Thu, 15 May 2008 01:21:53 +0000 (14 21:21 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 17 May 2008 03:59:49 +0000 (16 23:59 -0400) | ||
| tree | 78d2568c122c380f95c9c1de952338fb14ac3428 | treesnapshot (tar.gz zip) |
| parent | 1d627b30e61439aadcd303f8d9f3994e2ff94a77 | commitdiff |
Make it easier for RevWalk subclasses to override reset, dispose
With all of the different variants of reset() it can be confusing
to a subclass author which one they should actually override in
their own code to ensure cleanup actions are correctly taken for
member data. By marking most of the methods final and making the
real work method protected and non-final we can make it fairly
clear to the subclass writer what the safe override point is.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
With all of the different variants of reset() it can be confusing
to a subclass author which one they should actually override in
their own code to ensure cleanup actions are correctly taken for
member data. By marking most of the methods final and making the
real work method protected and non-final we can make it fairly
clear to the subclass writer what the safe override point is.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| org.spearce.jgit/src/org/spearce/jgit/revwalk/RevWalk.java | diffblobblamehistory |