\until }
- The event is initialized to fire eery \a interval nanoseconds. The traffic is routed 'across'
+ The event is initialized to fire every \a interval nanoseconds. The traffic is routed 'across'
the timer which controls the traffic. This routing lets the module automatically handle
throttling events. The timer is registered to call RateFilter::timeout().
additionally needs erase() and insert(). The container policy will also need the
element_type, parser_type and container_type typedefs.
- \see \ref Parse_List
+ \see \ref ListParser
*/
struct ExampleListPolicy
{
/** \brief Example of a list iterator policy. ONLY FOR EXPOSITION.
\see \ref ExampleListPolicy \n
- \ref Parse_List
+ \ref ListParser
*/
struct iterator_policy
{
/** \brief Example of a list container policy. ONLY FOR EXPOSITION
\see \ref ExampleListPolicy \n
- \ref Parse_List
+ \ref ListParser
*/
struct container_policy
{
arbitrary incorrect value otherwise.
\pre Field \a name preceded by fixed size fields only
- \param[in] field or label name
+ \param[in] name field or label name
\returns compile-time constant offset of the field from parsers start
\hideinitializer
*/
<em>Runtime</em> configuration on the other hand deals with routing all those messages, which
are enabled at compile time to the logging targets. If a message is not routed, it will be
discarded. This allows to additionally disable messages at run-time. Message routing is managed
- via the \ref Targets interface.
+ via the ::Target interface.
\section config_compile Compile time configuration
any necessary workarounds.
So, instead of <tt>\#include <boost/test/auto_unit_test.hpp></tt>, you should always write
- <tt>\#include "../Utils/auto_unit_test.hh"<tt> (with possibliy adjusted path).
+ <tt>\#include "../Utils/auto_unit_test.hh"</tt> (with possibliy adjusted path).
*/
#ifndef HH_auto_unit_test_