Ensure that UNMARSHAL is called with a destination class that uses one of the UNMARSHALLABLE metaclass subclasses. check-in: 2f9c3fb19d user: alexa tags: trunk

Also ensure the proper metaclasses are being used before marshalling objects. check-in: 54bc9fc07d user: alexa tags: trunk

* Breaking change: All type predicates in the CL-REMIMARSHAL-JSON and
CL-REMIMARSHAL-YAML packages have been combined and moved into the base
CL-REMIMARSHAL package.
* Breaking change: Fixed the spelling of various classes.
* Breaking change: Custom slot unmarshal functions now require three
arguments in this order: the data to be unmarshalled, the class instance
the data is getting stored into, and the slot the data is getting stored
into.
* Added support for SINGLE-FLOAT and DOUBLE-FLOAT slots.
* Properly implemented support for 24-bit signed and unsigned integers.
* Added the NORMALIZE-BOOLEAN, NORMALIZE-BOOLEAN?, NORMALIZE-BOOLEAN-LIST,
and NORMALIZE-BOOLEAN?-LIST utility functions.
* Added the CL-REMIMARSHAL-UTILS package and system. This provides a large
set of predefined marshalling and unmarshalling functions for various
common cases where you may want to use NIL for null values instead of
:NULL.
* The JSON-UNMARSHALLABLE and YAML-UNMARSHALLABLE meta classes now both
inherit from a base UNMARSHALLABLE class. The same applies for their
corresponding slot classes.
* Added the VALID-MARSHAL-TYPE-FOR-CLASS generic function.
* All systems except the tests system now use CL-SDM-ASDF.
* Tests have been greatly expanded.

This update was done in bulk due to various interdependencies. check-in: 436ecab7d6 user: alexa tags: trunk, v0.4.0