Adding overloads for cereal::JSONINputArchive(long & value) and
cereal::JSONINputArchive(unsigned long & value) to fix a compile issue
on OS X with clang 3.3 and libc++. This addresses issue #81. Please
check to make sure this works on the rest of the standard compilers
before closing.
Still some kinks to work out in regards to trait checks on a non-member
load_minimal that accepts everything as template parameters and does
enable_if style checks
Even though there is currently no need to use this archive parameter, it is now
passed to the various minimal serialization functions instead of simply being
a template parameter.
The reason for this was ultimately allow for correct name-lookup of the functions
using ADL when the type was unable to provide this (e.g. a generic serialize function
for enums written in the cereal namespace).
Also fixed some issues with GCC 4.7 and the various traits that warn if the type for the
load isn't passed by const ref. Had to use a workaround found here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51213 (=delete instead of private).
The following preprocessor defines have been added:
- CEREAL_SERIALIZE_FUNCTION_NAME
- CEREAL_SAVE_FUNCTION_NAME
- CEREAL_LOAD_FUNCTION_NAME
These defines specifiy the name of the cereal serialization/deserialization
functions so that they can be customised by users. This is especially useful if
the user would like to have capitialized function names.
If someone attempts to have both a versioned and non-versioned serialization
function, they will get a compile time error.
relates to improvements in #23
Also fixed a bug with some type traits that would erroneously return true if
an odd number of boolean variables were true when the desired behavior was to return
false if more than one boolean variable was true.
Need to revise the no matching serialization to properly fire if a type is specialized
but has both versioned and non-versioned functions of the specialization type.
longs should now properly serialize under 32 or 64 bit machines.
long long, unsigned long long, and long double now serialize as base10
strings instead of base64.
see issue #72
Modified the polymorphic saving of pointers to use a second
shared_ptr to manage the refcount of the wrapper proper polymorphic
shared_ptr (previously we were using an empty deleter). The result of
this is that the wrapper doesn't actually manage the pointer it holds,
it just allows access to it so long as there is still a refcount in
the second refcount pointer.
Modified the polymorphic wrapper and enable shared from this state
saver to be RAII style.
