Best practice: ordering of public/protected/private within the class definition?

In Clean Code, Robert C. Martin advises coders to always put member variables at the top of the class (constants first, then private members) and methods should be ordered in such a way so that they read like a story that doesn’t cause the reader to need to jump around the code too much. This is a more sensible way to organize code rather than by access modifier.

stackoverflow

Leave a Reply

Your email address will not be published. Required fields are marked *