Reuse Implies Coupling

From WikiContent

Revision as of 08:24, 8 October 2008 by Kmarquardt (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Do not make your code depend on some file that is intended to change with project's progress.

It is very convenient to have a global file that lists all error codes in the system. When starting the new component, you proudly add a handful: look, I am a part of this! Only to find you colleagues to mourn about the extra build time. How dare you change this file?

Couldn't you just do what everybody does:

* reuse some error codes that are already in there.
* when existing codes don't match the intended meaning, document their specific meaning in your component documentation.

The error.h file was intended to provide a great place to look for the meaning of codes. At the same time, it is a central component that is intended to change as the project proceeds. So it is your base, but it is quicksand.

How to get out? Consider this:

* real generic error messages (in the style of stl exceptions)
* a distint error.h file per component
Personal tools