On some systems (such as OS X), use64bitint can be true even when in 32-bit mode.
This adds the ability to pass any ISO 8601 string to the RPC::XML::datetime_iso8601 constructor.
Non-64-bit systems will skip, rather than fail, these tests.
These are the changes to the test suites to increase coverage of the code.
This revealed problems with i8 smart-encoding, but I don't have a fix for it yet. Marked two tests as "TODO" so their failure is acceptable for now.
…nstruction of dateTime.iso8601 data-types.
…pected. This led to adding use of Scalar::Util and cleaning up the places where I was still doing "UNIVERSAL::isa(...)" hacks to test refs without the risk of directly calling ->isa() on a potentially-unblessed ref.
…o conform to the XML-RPC spec, as it does not allow for exponential notation. This also required changes to the tests, as values were no longer being auto-truncated at 5 decimal places. Also finished cleaning up the t/10_data.t test suite with diagnostic messages on the tests that had not previously gotten them.
…an error when a reference-type is passed in that cannot be converted. Added two tests to cover this, and took the opportunity to convert 10_data.t to Test::More.
in the creation of temporary file names if a test script is run directly from the "t" directory. While at it, added a line with the Subversion "Id" keyword and set the "svn:keywords" property on all test scripts.
…de() hack that tries to match bare Perl data to RPC classes.
…errors. Patch from Juan Camacho.
… method of RPC::XML::string. Trying to encode the literal string "0" would result in a null string. The patches provided the fix and a specific test-case for the related suite.
smart_encode helper-routine to deal with blessed references. Anything that is derived from HASH or ARRAY is encoded as a struct or array, respectively. Anything derived from SCALAR is dereferenced and encoded as per usual. Carried this over to the class constructors, with special attention to the RPC::XML::simple_type class. Added tests to the suite for all of this, as well.
… also made several syntax-pedantry changes.
… will have to derive the Content-Length header. These changes implement a length() method in all data classes, adds docs and adds tests.
completeness as possible.