2007/5/25, Petter Reinholdtsen <[EMAIL PROTECTED]>:
testsuite/libamf.all/test_number.cppamfnum_t *num; num = amf_obj.extractNumber(buf); if ((((char *)num)[6] == -16) && (((char *)num)[7] == 0x3f)) { runtest.pass("Extracted Number AMF object"); } else { runtest.fail("Extracted Number AMF object"); } The test fail on s390, as it would on all architectures with a different endianness than the authors machine.
I don't get it. It's checking for 0xf03f (hence the idiotic -16), and in the AMF stream numbers are 64-bit bigendian. But presumable extractNumber() converts to native endian. So why does the big-endian f0 3f test succeed on little-endian hosts and fail on big-endian ones? M _______________________________________________ Gnash mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash
