On Sun, Feb 14, 2010 at 6:46 AM, Sean Owen <sro...@gmail.com> wrote:
>
>
> I am also a big fan of declaring classes (or more narrowly, certain
> methods)
> final by default. Design for extension or prohibit if says the wise
> Reverend
> Bloch. But this isn't something I'd actively foist on anyone since it needs
> judgment about design intent.
>

I second (or third, or fourth) Benson, Ted, and Grant's assertion that in
ASF
projects, this more often bites us on the ass than helps.


>
> I actually used to write method params final by default but stopped, even
> though I like what it promotes. Nobody is pushing that though.


-1 on that from me.  Its fine in principal, but it pisses me off to no end
when
I see a reason to override an open-source project's method that the author
didn't realize, and see that I have to work around this by copy/paste or
by ripping open the jar and recompiling my own version which removes the
final.

  -jake

Reply via email to