[mlpack-git] master: Update comment for accuracy; I should have been more specific when I wrote it. (a6f20af)

gitdub at mlpack.org gitdub at mlpack.org
Mon Apr 18 13:44:28 EDT 2016


Repository : https://github.com/mlpack/mlpack
On branch  : master
Link       : https://github.com/mlpack/mlpack/compare/8a249cf02c9bc109a32235126c42cf69a10fae95...7e0e6ea1e3a7d242305a5a6a6e9730c5c3bfdc98

>---------------------------------------------------------------

commit a6f20af3092f3a6aaa810f2fb742ed2eddaebad9
Author: Ryan Curtin <ryan at ratml.org>
Date:   Mon Apr 18 10:44:28 2016 -0700

    Update comment for accuracy; I should have been more specific when I wrote it.


>---------------------------------------------------------------

a6f20af3092f3a6aaa810f2fb742ed2eddaebad9
 src/mlpack/tests/rectangle_tree_test.cpp | 4 ----
 src/mlpack/tests/tree_traits_test.cpp    | 6 +++---
 2 files changed, 3 insertions(+), 7 deletions(-)

diff --git a/src/mlpack/tests/rectangle_tree_test.cpp b/src/mlpack/tests/rectangle_tree_test.cpp
index 15f859e..42092b6 100644
--- a/src/mlpack/tests/rectangle_tree_test.cpp
+++ b/src/mlpack/tests/rectangle_tree_test.cpp
@@ -21,10 +21,6 @@ using namespace mlpack::metric;
 
 BOOST_AUTO_TEST_SUITE(RectangleTreeTest);
 
-// Be careful!  When writing new tests, always get the boolean value and store
-// it in a temporary, because the Boost unit test macros do weird things and
-// will cause bizarre problems.
-
 // Test the traits on RectangleTrees.
 
 BOOST_AUTO_TEST_CASE(RectangleTreeTraitsTest)
diff --git a/src/mlpack/tests/tree_traits_test.cpp b/src/mlpack/tests/tree_traits_test.cpp
index 0de745f..e7b4925 100644
--- a/src/mlpack/tests/tree_traits_test.cpp
+++ b/src/mlpack/tests/tree_traits_test.cpp
@@ -23,9 +23,9 @@ using namespace mlpack::metric;
 
 BOOST_AUTO_TEST_SUITE(TreeTraitsTest);
 
-// Be careful!  When writing new tests, always get the boolean value and store
-// it in a temporary, because the Boost unit test macros do weird things and
-// will cause bizarre problems.
+// Be careful!  When writing new tests, always get the boolean value of each
+// trait and store it in a temporary, because the Boost unit test macros do
+// weird things and will cause bizarre problems.
 
 // Test the defaults.
 BOOST_AUTO_TEST_CASE(DefaultsTraitsTest)




More information about the mlpack-git mailing list