"Bryan Tong Minh" bryan.tongminh@gmail.com wrote in message news:fd5886130908120137h13b0aad9xdd2f05c8a362cc4e@mail.gmail.com...
On Wed, Aug 12, 2009 at 2:38 AM, Chadinnocentkiller@gmail.com wrote:
My point is that not declaring visibility on new code (ie: leaving everything public) is poor form. It usually doesn't take very long to make the decision about what scope to put a function or variable in, and it can always be changed later if the choice was wrong.
Well, you can always go up (private>protected>public), but not necessarily go down without possibly breaking things you are unaware of.
True - and not specifying a scope means the visibility defaults to public. Therefore requiring a scope to be declared can only be a good thing.
- Mark Clements (HappyDog)