On Sat, Jan 24, 2009 at 3:38 PM, Rick McGuire <object.r...@gmail.com> wrote: > I've sort of been ignoring this issue since Rainer reported the same > for 64-bit AIX. This is largely because I was already a bit burded > out with dealing with the twists and turns of floating point. It > appears that basically this is getting converted to a double value, > so it doesn't end up being an exact match. I've checked in some > changes for those test cases that *might* fix the problem.
Thanks Rick. The changes did clear up the failures. This is using a 64-bit build on Windows: ooTest Framework - Automated Test of the ooRexx Interpreter Interpreter: REXX-ooRexx_4.0.0(MT) 6.03 24 Jan 2009 ooRexxUnit: 2.0.0_3.2.0 ooTest: 1.0.0_4.0.0 Tests ran: 19022 Assertions: 551702 Failures: 0 Errors: 0 Skipped files: 1 File search: 00:00:05.812000 Suite construction: 00:00:02.203000 Test execution: 00:03:47.375000 Total time: 00:03:56.312000 The skipped file is an oleObject test because I don't have Excel installed on this system. I guess I should add some text in the print out showing the addressing mode of the build. -- Mark Miesfeld ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
