Version 5 (modified by 13 years ago) ( diff ) | ,
---|
Coding Style
How MoleCuilder code should look like
Below you find a brief but hopefully complete list on how the code of espack should look like:
- identate by two spaces, never tabs
- Code Style from Eclipse, see ESPACK_codestyle.xml:
/* * A sample source file for the code formatter preview */ #include <math.h> class Point { public: Point(double xc, double yc) : x(xc), y(yc) { } double distance(const Point& other) const; double x; double y; }; double Point::distance(const Point& other) const { double dx = x - other.x; double dy = y - other.y; return sqrt(dx * dx + dy * dy); }
Coding hints
Some hints on good code vs. bad code
end of stream checking
Using
std::inputstream in; while (!in.eof()) { .. }is bad. Rather one should use
std::inputstream in; while (in.getline(...)) { .. }or
std::inputstream in; for(int j; in >> j;;) { .. }or
std::inputstream in; in >> j; if (in.fail()) ..This involves some extra typing but ensures that in case of faulty streams the error is properly pointed at.
Use of new/delete
Use of return
The return statement should look like this
return bar; return (foo && bar);
and not like
return (bar); return(foo);
Attachments (1)
-
ESPACK_codestyle.xml
(16.0 KB
) - added by 15 years ago.
Coding stylesheet for Eclipse
Download all attachments as: .zip
Note:
See TracWiki
for help on using the wiki.