Skip to content
Snippets Groups Projects
This project is mirrored from https://git.alchemyviewer.org/alchemy/alchemy-next.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
  1. Oct 23, 2014
    • Nat Goodspeed's avatar
      Bring in new TUT library build. Clean up ensure_equals() overloads. · 918e2b62
      Nat Goodspeed authored
      The new TUT library build eliminates the ambiguity about ensure_equals(const
      char*, ...) versus ensure_equals(const std::string&, ...). Now it's all based
      on const std::string&. Remove pointless const char* overloads and ambiguous
      forwarding templates.
      With clang in Xcode 6, any new datatypes we intend to use with ensure_equals()
      must have operator<<(std::ostream&, datatype) declared BEFORE lltut.h
      #includes tut.hpp. Reorder code in certain test source files to guarantee that
      visibility.
      918e2b62
    • Nat Goodspeed's avatar
      Fix Xcode 6 compile errors relating to tut::ensure_equals() overloads. · 642c334e
      Nat Goodspeed authored
      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.
      642c334e
    • callum_linden's avatar
  2. Oct 22, 2014
  3. Oct 21, 2014
  4. Oct 20, 2014
Loading