[mkgmap-dev] Merge from the multipolygon branch.From Mark Burton markb at ordern.com on Mon Sep 14 22:11:14 BST 2009
Steve, > > Why zap the final? It was there for a reason. > > And what would that reason be? It explicitly declares that the method can never be redefined and therefore is a candidate for inline expansion. Obviously, the method is implicitly final anyway due to it being private but adding the final means that if the method is ever made non-private it will still be capable of being optimised. That's my reason, what's yours? Cheers, Mark
- Previous message: [mkgmap-dev] Merge from the multipolygon branch.
- Next message: [mkgmap-dev] Merge from the multipolygon branch.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list