From: Stephen Crawley <crawley@dstc.edu.au>
To: Brian Jones <cbj@gnu.org>
Cc: mauve-discuss@sources.redhat.com
Subject: Problem with CollationElementIterator.jdk11 testcases
Date: Wed, 11 Jun 2003 14:19:00 -0000 [thread overview]
Message-ID: <200306111419.h5BEJ3FK014132@piglet.dstc.edu.au> (raw)
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
next reply other threads:[~2003-06-11 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:19 Stephen Crawley [this message]
2003-06-11 22:37 ` Brian Jones
2003-06-11 23:42 ` Stephen Crawley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200306111419.h5BEJ3FK014132@piglet.dstc.edu.au \
--to=crawley@dstc.edu.au \
--cc=cbj@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).