Using snippetlineno instead of snippet to make it clear that those are code snippets for that example.

Author: cpscotti

examples/counterwithreset.cpp

@@ -75,7 +75,7 @@ digraph GraphAnalyzer {
  * `Reset` TopicState should be evaluated in the next Evaluation pass and not
  * in the current one. In such cases it is reasonable to put the responsibility
  * for closing the loop on the writer of `ResetDetector`:
- * @snippet counterwithreset.cpp Reset Detector
+ * @snippetlineno counterwithreset.cpp Reset Detector
  *
  * In cases where downstream parts of the graph also subscribe to the
  * TopicState used in the feedback loop, DetectorGraph::Lag should be used
@@ -84,9 +84,9 @@ digraph GraphAnalyzer {
  *
  * @section Graph
  * The graph instantiated and evaluation code is unaffected. Both
- @snippet counterwithreset.cpp CounterWithResetGraph
+ @snippetlineno counterwithreset.cpp CounterWithResetGraph
  * and
- @snippet counterwithreset.cpp main
+ @snippetlineno counterwithreset.cpp main
  * work in the same way as with simple graphs.
  *
  * Running the program produces:

examples/helloworld.cpp

@@ -45,26 +45,26 @@ using std::endl;
  * DetectorGraph::TopicState.
  *
  * For the 'input' to our system we'll declare a `TemperatureSample` TopicState:
- @snippet helloworld.cpp Input Topic
+ @snippetlineno helloworld.cpp Input Topic
  * The important here is that this `struct` inherits TopicState and that it has
  * data field(s).
  *
  * Next we define the 'output'; another struct that also inherits
  * DetectorGraph::TopicState and has data fields:
- @snippet helloworld.cpp Output Topic
+ @snippetlineno helloworld.cpp Output Topic
  *
  * @section Detector
  * Now we just need to fill in the gap; the Detector that creates
  * `OverheatingState` from `TemperatureSample`:
  * two.
- @snippet helloworld.cpp Detector
+ @snippetlineno helloworld.cpp Detector
  *
  * @section Graph
  * The final plumbing is to add our newly created Detector to a
  * DetectorGraph::Graph.
  * Depending on the situation this can be done in different ways but here's the
  * simplest:
- @snippet helloworld.cpp Adding to a Graph
+ @snippetlineno helloworld.cpp Adding to a Graph
  *
  * With that the Graph instance will internally create the following graph:
  *
@@ -90,7 +90,7 @@ digraph GraphAnalyzer {
  * @section Usage
  * Finally, using the graph is done by Pushing data in, evaluating the graph
  * and checking outputs:
- @snippet helloworld.cpp Basic Graph Usage
+ @snippetlineno helloworld.cpp Basic Graph Usage
  *
  * Running the program then gives:
  \verbatim
@@ -104,10 +104,10 @@ IsOverheating = true
  * subsequent inspection steps.
  * For the example above, the DetectorGraph::ProcessorContainer implementation
  * would be:
- @snippet helloworld.cpp ProcessorContainer
+ @snippetlineno helloworld.cpp ProcessorContainer
  *
  * And then usage would be like:
- @snippet helloworld.cpp Using ProcessorContainer
+ @snippetlineno helloworld.cpp Using ProcessorContainer
  *
  *
  \verbatim

examples/portuguesetranslator.cpp

@@ -52,11 +52,11 @@ using std::endl;
  *
  * In this example, the `TranslationDictionary` TopicState carries a large,
  * immutable object and does so using a shared_ptr<const T>:
- @snippet portuguesetranslator.cpp Immutable Shared Memory TopicState
+ @snippetlineno portuguesetranslator.cpp Immutable Shared Memory TopicState
  *
  * A different example that also uses this pattern is
  * [Fancy Vending Machine](@ref fancyvendingmachine.cpp):
- @snippet fancyvendingmachine.cpp Immutable Shared Memory TopicState
+ @snippetlineno fancyvendingmachine.cpp Immutable Shared Memory TopicState
  *
  * @section Architecture
  * This sample implements the following graph:

examples/robotlocalization.cpp

@@ -45,7 +45,7 @@ using namespace Eigen;
  * This localization algorithm depends on a feedback-loop in that the output of
  * one graph evaluation (i.e. `LocalizationBelief`) is used as an input for the
  * next one (i.e. `Lagged<LocalizationBelief>`):
- @snippet robotlocalization.cpp KalmanPoseCorrector Feedback Loop
+ @snippetlineno robotlocalization.cpp KalmanPoseCorrector Feedback Loop
  * Note that in this graph the TopicState where the feedback loop closes is a
  * legitimate output in itself and it's very likely that new Detectors in the
  * graph would subscribe to it. In cases like this the use of

examples/trivialvendingmachine.cpp

@@ -37,7 +37,7 @@ using std::endl;
  *
  * @section tts Trivial TopicStates
  * A _Trivial TopicState_ has no data fields:
- @snippet trivialvendingmachine.cpp Trivial TopicState
+ @snippetlineno trivialvendingmachine.cpp Trivial TopicState
  * These are sometimes useful to represent parameter-less signals, timeouts etc.
  *
  * @section nts Named TopicStates
@@ -58,20 +58,20 @@ using std::endl;
  * [TopicStateIdType](@ref DetectorGraph::TopicStateIdType) and be different than
  * [TopicState::kAnonymousTopicState](@ref DetectorGraph::TopicState::kAnonymousTopicState)
  * (-1). An example would be:
- @snippet trivialvendingmachine.cpp Application-Specific Enum for Named TopicStates
+ @snippetlineno trivialvendingmachine.cpp Application-Specific Enum for Named TopicStates
  (`C++03` enums are fine too)
  *
  * Which then can be used in the overriding of TopicState::GetId for the desired
  * named TopicState:
- @snippet trivialvendingmachine.cpp Named TopicState
+ @snippetlineno trivialvendingmachine.cpp Named TopicState
  *
  * That then enables things like:
- @snippet trivialvendingmachine.cpp Inspecting Graph Output with Named TopicStates
+ @snippetlineno trivialvendingmachine.cpp Inspecting Graph Output with Named TopicStates
  *
  * @section dga GraphAnalyzer
  * Finally, this example also shows how to use DetectorGraph::GraphAnalyzer to
  * generate a GraphViz-compatible `.dot` representation of the graph:
- @snippet trivialvendingmachine.cpp Using GraphAnalyzer to Create dot file
+ @snippetlineno trivialvendingmachine.cpp Using GraphAnalyzer to Create dot file
  *
  * That .dot file when rendered generates the following graph:
  @dot "Trivial Vending Machine"