The test runner will generate a check-like output, indicating the
the results of each test script.
+
+=== Developers Guide
+
+Run doc/dev_guide.sh to generate /tmp/dev_guide.html, an annotated guide to
+the source tree.
+
* w3m from http://sourceforge.net/projects/w3m/ to build the plain text
manual
+* source-highlight from http://www.gnu.org/software/src-highlite/ to
+ generate the dev guide.
+
=== Building
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml,
but there are a few differences.
+* Each source directory should have a dev_notes.txt file summarizing the
+ key points for the code in that directory. These are built into the
+ developers guide.
+
=== Naming
* Use camel case for namespaces, classes, and types like WhizBangPdfChecker.
* Put author, description, etc. in separate comment(s) following the
license. Do not put such comments in the middle of the license foo.
+ Be sure to put the author line ahead of the header guard to exclude them
+ from the developers guide.
+
+* Each header should have a comment immediately after the header guard to
+ give an overview of the file so the user knows what's going on.
=== Logging
the various errors anyway or needlessly and ineffectively tries to do
something aobut them.
-
=== Macros (aka defines)
* In many cases, even in C++, use #define name "value" instead of a
// in foo.cc
#include "bar/bar.h"
+* Includes within installed headers should specify parent directory.
+
* Just because it is a #define doesn't mean it goes in a header.
Everything should be scoped as tightly as possible. Shared
implementation declarations should go in a separate header from the
public:
friend class PacketManager;
- // global plugin initializer. Called by LUA to add register codecs
+ // global plugin initializer
static void add_plugin(const struct CodecApi*);
// instantiate a specific codec with a codec specific Module
static void instantiate(const CodecApi*, Module*, SnortConfig*);