This is the mail archive of the java@gcc.gnu.org mailing list for the Java 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]

Re: java.util.Date.toString() really slow?

From: Tom Tromey <tromey at redhat dot com>
To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
Cc: Jeff Sturm <jsturm at one-point dot com>, Adam Megacz <gcj at lists dot megacz dot com>, java at gcc dot gnu dot org
Date: 04 Jun 2002 12:57:10 -0600
Subject: Re: java.util.Date.toString() really slow?
References: <Pine.LNX.4.10.10206031118180.23728-100000@mars.deadcafe.org> <3CFC3199.5080005@waitaki.otago.ac.nz>
Reply-to: tromey at redhat dot com

>>>>> "Bryce" == Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:

Bryce> Presumably it would be reasonable to cache negative results for
Bryce> resource bundle (and class?) lookups. People don't expect to be
Bryce> able to dynamically add new resource bundles to a running
Bryce> application, right?

I wonder.  Maybe someone could test the JDK and see what it does.  You
could imagine wanting to dynamically add resource bundles to some
long-running application like a web server -- it isn't a completely
absurd idea.

Tom

Follow-Ups:
- Re: java.util.Date.toString() really slow?
  - From: Jeff Sturm

References:
- Re: java.util.Date.toString() really slow?
  - From: Jeff Sturm
- Re: java.util.Date.toString() really slow?
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]