From: Justin Viiret <justin.viiret@intel.com>
Date: Thu, 9 Mar 2017 22:42:57 +0000 (+1100)
Subject: ng_corpus_generator: restore use of boost::next()
X-Git-Tag: v4.5.0^2~174
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3e597e85ffcebcb2d11b80282f7ace3ed98c7fcb;p=thirdparty%2Fvectorscan.git

ng_corpus_generator: restore use of boost::next()

libc++ checks for forward_iterator_tag in std::next(), which isn't
provided by our (Boost-derived) ue2_graph iterators.
---

diff --git a/util/ng_corpus_generator.cpp b/util/ng_corpus_generator.cpp
index f2e8f7f9..72c13e84 100644
--- a/util/ng_corpus_generator.cpp
+++ b/util/ng_corpus_generator.cpp
@@ -53,6 +53,8 @@
 #include <sstream>
 #include <vector>
 
+#include <boost/utility.hpp>
+
 using namespace std;
 using namespace ue2;
 
@@ -194,7 +196,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 (std::next(ai) == ae) {
+            if (boost::next(ai) == ae) {
                 new_path = std::move(p);
             } else {
                 new_path = make_unique<VertexPath>(*p);