This is the mail archive of the mauve-discuss@sources.redhat.com mailing list for the Mauve project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Hi Brian, I've been trying to work out why Classpath (over Kissme) is failing 16 test in gnu.testlet.java.text.CollationElementIterator.jdk11. For example: FAIL: gnu.testlet.java.text.CollationElementIterator.jdk11: next() 0 (number 1) FAIL: gnu.testlet.java.text.CollationElementIterator.jdk11: primaryOrder() 0 (number 1) Examining the testcase code, and comparing the test results with those for various Sun JDK's, it seems that the Classpath implementation is returning different collation key values. The testcase is expecting the JDK value and is barffing. But I don't think that this is correct. Nothing I could see in the Sun javadocs that specifies what the precise key values should have. Rather, the specification says that the key values simply have to have specific ordering characteristics. What do you think? -- Steve
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |