diff options
author | Nat Goodspeed <nat@lindenlab.com> | 2014-10-23 08:44:42 -0700 |
---|---|---|
committer | Nat Goodspeed <nat@lindenlab.com> | 2014-10-23 08:44:42 -0700 |
commit | 642c334efa2dbd0bafca5b0dbb11a986cd5ab4a9 (patch) | |
tree | f332d919baaf82e189b589906e33b42cecc26a45 /indra/test/lltut.cpp | |
parent | e66844570e42601c1c653d7169c694fd8310fb56 (diff) |
Fix Xcode 6 compile errors relating to tut::ensure_equals() overloads.
lltut.h declares a number of ensure_equals() overloads for various data types,
notably the types supported by LLSD. We expect these to be called by tut code.
But the tut code in question is in a template in tut.hpp -- which was
#included BEFORE the overloads were declared. Previous C++ compilers have
evidently made multiple passes, collecting the relevant overloads before
attempting to compile the template bodies. clang does not, complaining that
the overloads must be declared before the tut.hpp template code that
references them. Reordering parts of lltut.h seems to address that problem.
For similar reasons, test programs that use StringVec.h and its operator<<()
must #include StringVec.h before lltut.h.
Add ensure_equals(const std::string&, const LLSD::Binary&, const LLSD::Binary&)
overload. The sloppy mix of (const char*, ...) and (const std::string&, ...)
overloads bothers me, since for many of those ... types we seem to have to
duplicate them.
Diffstat (limited to 'indra/test/lltut.cpp')
-rwxr-xr-x | indra/test/lltut.cpp | 25 |
1 files changed, 19 insertions, 6 deletions
diff --git a/indra/test/lltut.cpp b/indra/test/lltut.cpp index a183cef9a9..2730fb34d7 100755 --- a/indra/test/lltut.cpp +++ b/indra/test/lltut.cpp @@ -52,12 +52,25 @@ namespace tut actual.asString(), expected.asString()); } + // The lexical param types here intentionally diverge from the declaration + // in our header file. In lltut.h, LLSD is only a forward-declared type; + // we have no access to its LLSD::Binary nested type, and so must restate + // it explicitly to declare this overload. However, an overload that does + // NOT match LLSD::Binary does us no good whatsoever: it would never be + // engaged. Stating LLSD::Binary for this definition at least means that + // if the LLSD::Binary type ever diverges from what we expect in lltut.h, + // that divergence will produce an error: no definition will match that + // declaration. void ensure_equals(const char* msg, - const std::vector<U8>& actual, const std::vector<U8>& expected) + const LLSD::Binary& actual, const LLSD::Binary& expected) { - std::string s(msg); - - ensure_equals(s + " size", actual.size(), expected.size()); + ensure_equals(std::string(msg? msg : ""), actual, expected); + } + + void ensure_equals(const std::string& msg, + const LLSD::Binary& actual, const LLSD::Binary& expected) + { + ensure_equals(msg + " size", actual.size(), expected.size()); std::vector<U8>::const_iterator i, j; int k; @@ -65,14 +78,14 @@ namespace tut i != actual.end(); ++i, ++j, ++k) { - ensure_equals(s + " field", *i, *j); + ensure_equals(msg + " field", *i, *j); } } void ensure_equals(const char* m, const LLSD& actual, const LLSD& expected) { - ensure_equals(std::string(m), actual, expected); + ensure_equals(std::string(m? m : ""), actual, expected); } void ensure_equals(const std::string& msg, const LLSD& actual, |