This is the mail archive of the java-patches@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: Patch: merge File.toURI() from Classpath

From: Dalibor Topic <robilad at kaffe dot org>
To: Bryce McKinlay <mckinlay at redhat dot com>
Cc: Chris Pickett <chris dot pickett at mail dot mcgill dot ca>, crawley at piglet dot dstc dot edu dot au, Stephen Crawley <crawley at dstc dot edu dot au>, classpath at gnu dot org, David Daney <ddaney at avtrex dot com>, java-patches at gcc dot gnu dot org
Date: Wed, 07 Jul 2004 20:19:59 +0200
Subject: Re: Patch: merge File.toURI() from Classpath
References: <69397FFCADEFD94F8D5A0FC0FDBCBBDEF484@avtrex-server.hq.avtrex.com> <40EB99FD.7010207@mail.mcgill.ca> <40EC3311.2090906@redhat.com>

Bryce McKinlay wrote:

Again, these exceptions should be documented as part of our API documentation. They are exceptions that should _never_ happen. No call from the application should cause them to be thrown, thus they are not part of the API. If they are ever thrown, then there is a bug in classpath. Nevertheless, applications should have the ability to try and continue in the face of classpath bugs if they need fault tolerance.

Can't we just use assertions for things that should never happen?

cheers,
dalibor topic

Follow-Ups:
- Re: Patch: merge File.toURI() from Classpath
  - From: Bryce McKinlay

References:
- RE: Patch: merge File.toURI() from Classpath
  - From: David Daney
- Re: Patch: merge File.toURI() from Classpath
  - From: Chris Pickett
- Re: Patch: merge File.toURI() from Classpath
  - From: Bryce McKinlay

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