public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dalibor Topic <robilad@yahoo.com>
To: Anthony Green <green@redhat.com>, Stephen Crawley <crawley@dstc.edu.au>
Cc: Mark Wielaard <mark@klomp.org>, Dalibor Topic <robilad@yahoo.com>,
	mauve-discuss@sources.redhat.com, crawley@piglet.dstc.edu.au
Subject: Re: 600+ BigDecimal tests
Date: Mon, 20 Jan 2003 09:48:00 -0000	[thread overview]
Message-ID: <20030120094853.27854.qmail@web10008.mail.yahoo.com> (raw)
In-Reply-To: <1043021531.2354.27.camel@escape>


--- Anthony Green <green@redhat.com> wrote:
> On Sun, 2003-01-19 at 15:39, Stephen Crawley wrote:
> >   * Some of the other tests check exception
> message strings, and are
> >     failing because the messages are different. 
> > 
> > I don't know whether this is a bug or not.  Is
> Classpath aiming to
> > give the same exception messages as the Sun JDK
> implementation ???
> 
> I don't think so (could be wrong).  I suppose we
> should remove these
> tests.

I'd vote for a change to catch the exception and
ignore the message. After all, free implementations
may (have) come up with more understandable,
localized, superior messages to those provided by
Sun's implementation. It would be counterproductive to
force them to change them  to Sun's version.

> > 
> >   * The 'has001' failure is due to differences in
> the way that 
> >     Classpath and the SUN JDK are calculating
> hashcodes.
> > 
> > I don't know whether this is a bug or not.  Is
> Classpath aiming to
> > give the same hash code values as the Sun JDK
> implementation ???
> 
> I know that some people have spent time figuring out
> how Sun hashes
> various objects, although I don't know if this is a
> policy. 

I think the essential question here is: can having
different hash methods bite you in some way? Beside
obvious hashing performance considerations, I doubt
it.

best regards,
dalibor topic

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

  parent reply	other threads:[~2003-01-20  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-22 14:58 Anthony Green
2003-01-03  1:35 ` Mark Wielaard
2003-01-17 19:26   ` Mark Wielaard
2003-01-18 15:27     ` Dalibor Topic
2003-01-18 16:05       ` Mark Wielaard
2003-01-19 23:40         ` Stephen Crawley
2003-01-20  0:09           ` Anthony Green
2003-01-20  0:25             ` Stephen Crawley
2003-01-20  1:21               ` Artur Biesiadowski
2003-01-20  2:11                 ` Stephen Crawley
2003-01-20  9:48             ` Dalibor Topic [this message]
2003-01-20  0:06   ` Anthony Green

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=20030120094853.27854.qmail@web10008.mail.yahoo.com \
    --to=robilad@yahoo.com \
    --cc=crawley@dstc.edu.au \
    --cc=crawley@piglet.dstc.edu.au \
    --cc=green@redhat.com \
    --cc=mark@klomp.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).