--- Comment #7 from Dejan Lekic <> 2012-04-21 10:28:29 PDT 
I see your point.
However, I disagree - one should learn the language, and understand where and
how "final:" can be used. I have no problems with the current situation.
Compiler also generates a helpful error message that can be understood by
anyone. I personally never use public: final: private: etc... I prefer
public{}, private{}, etc. or use these per-declaration.

@Stewart Gordon
Neither are good - the second approach makes it possible to easily make a
mistake if developer is not pedantic enough. Say a class has buch of various
methods - and in the middle of it developer decides to add a variable... I know
- bad programming practice but still possible... However, developers typically
group variables and methods, so I guess it is OK.

As I said, I like the current approach when compiler generates a descriptive

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to