From: Justin Viiret <justin.viiret@intel.com>
Date: Tue, 7 Mar 2017 23:42:28 +0000 (+1100)
Subject: ng_corpus_generator: use std::next, not boost::next
X-Git-Tag: v4.5.0^2~176
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=26ec7dd332bae9af2ddf1ae0b590cc49944ec588;p=thirdparty%2Fvectorscan.git

ng_corpus_generator: use std::next, not boost::next
---

diff --git a/util/ng_corpus_generator.cpp b/util/ng_corpus_generator.cpp
index 8692a323..f2e8f7f9 100644
--- a/util/ng_corpus_generator.cpp
+++ b/util/ng_corpus_generator.cpp
@@ -194,7 +194,7 @@ void findPaths(const NGHolder &g, CorpusProperties &cProps,
             // If we've got no further adjacent vertices, re-use p rather than
             // copying it for the next path.
             unique_ptr<VertexPath> new_path;
-            if (boost::next(ai) == ae) {
+            if (std::next(ai) == ae) {
                 new_path = std::move(p);
             } else {
                 new_path = make_unique<VertexPath>(*p);