cleaning up some limits usage in extproc

rethinkdb · Feb 20, 2014 · d3205c7 · d3205c7
1 parent dbd7680
commit d3205c7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/src/extproc/js_job.cc b/src/extproc/js_job.cc
@@ -13,6 +13,7 @@
 #endif
 
 #include <cmath>
+#include <limits>
 
 #include "rdb_protocol/rdb_protocol_json.hpp"
 #include "rdb_protocol/pseudo_time.hpp"
@@ -27,7 +28,7 @@
 
 
 const js_id_t MIN_ID = 1;
-const js_id_t MAX_ID = UINT64_MAX;
+const js_id_t MAX_ID = std::numeric_limits<js_id_t>::max();
 
 // Picked from a hat.
 #define TO_JSON_RECURSION_LIMIT  500

diff --git a/src/extproc/js_runner.cc b/src/extproc/js_runner.cc
@@ -7,9 +7,6 @@
 
 const size_t js_runner_t::CACHE_SIZE = 100;
 
-const js_id_t MIN_ID = 1;
-const js_id_t MAX_ID = UINT64_MAX;
-
 // This class allows us to manage timeouts in a cleaner manner
 class js_timeout_t {
 public: