| News | |
 |
Latest |
|
Archive |
|
Community news |
| Articles | |
|
C++ |
|
Communities and Content |
|
Databases |
|
Editorials |
|
Emacs |
|
General |
|
HTML |
|
Java |
|
Notices |
|
PHP |
|
XML |
| Links | |
|
Apache |
|
C++ |
|
Database |
|
General |
|
HTML |
|
Java |
|
Javascript |
|
Linux |
|
Object oriented programming |
|
Open source |
|
Perl |
|
PHP |
|
Python |
|
Ruby |
|
SOAP |
|
XML |
|
Suggest a link |
| About | |
|
Advertise on zez |
|
Contribute |
|
Contact us |
|
About zez |
Coding Standards - Part 3 - What remains |
Name spaces
In order to avoid bad or too long class names, use name spaces to split and ground classes and functions. This means that two classes can have the same name as long as they exist in different name spaces, enabling you the use more intuitive names. However, before you start using name spaces make sure it will work on all platforms used in the project.
Classes
Classes should do only one thing and do it well. Split it into subclasses if it's too big. Use multiple inheritance sparingly, consider using a pointer to an object (this is often called composition) instead of inheriting it.
All member variables must be private. When access to member variables is required use functions, never use public or protected variables.
Helper functions should be private. Functions that don't access member variables or functions can be made static.
Comment List
| Topic: | Author: | Time: |
|---|---|---|
| Hacking URLS | TF Paschall | 15.12.2001 17:38 |
|
I notice that hacking off "article/" and "articleview/" from the zez.org URLs renders an empty page body.
|
||
