From c5f409deb009d7dfa8ec245d1b34bb73a150b269 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carsten=20Gr=C3=A4ser?= <graeser@dune-project.org>
Date: Thu, 3 Mar 2016 12:49:41 +0100
Subject: [PATCH] [doc] Mark new criterion mechanism as experimental
---
dune/solvers/solvers/criterion.hh | 5 +++++
dune/solvers/solvers/loopsolver.hh | 6 ++++++
2 files changed, 11 insertions(+)
diff --git a/dune/solvers/solvers/criterion.hh b/dune/solvers/solvers/criterion.hh
index cd5ed60d..54473242 100644
--- a/dune/solvers/solvers/criterion.hh
+++ b/dune/solvers/solvers/criterion.hh
@@ -10,6 +10,11 @@
#include <dune/common/stringutility.hh>
+
+/**
+ * \attention Everything contained in this headere is experimental and may change in the near future.
+ */
+
namespace Dune {
namespace Solvers {
diff --git a/dune/solvers/solvers/loopsolver.hh b/dune/solvers/solvers/loopsolver.hh
index 53220ca9..57e28cd8 100644
--- a/dune/solvers/solvers/loopsolver.hh
+++ b/dune/solvers/solvers/loopsolver.hh
@@ -63,6 +63,12 @@ public:
* This method forward all arguments to the constructor of
* Criterion. So you can pass a Criterion or any argument
* list supported by the Criterion constructors.
+ *
+ * Notice, that the old hard-wired criteria are still active.
+ * If you don't supply any criteria here, the you will get
+ * exactly the old behaviour.
+ *
+ * \attention This is an experimental feature that may still change in the near future.
*/
template<class... Args>
void addCriterion(Args&&... args)
--
GitLab