AssertionError.java: Merge with classpath, fixes HTML.
2002-09-16 Michael Koch <konqueror@gmx.de> * java/lang/AssertionError.java: Merge with classpath, fixes HTML. * java/rmi/server/LogStream.java: Merge with classpath, fixes some constants. * java/net/server/RemoteServer.java: Merge with classpath, adds serialVersionUID. * javax/naming/BinaryRefAddr.java: Merge with classpath, s/equal/equals/. * javax/naming/NamingException.java: Merge with classpath, fixed typo. * javax/naming/RefAddr.java: Merge with classpath, s/equal/equals/. * java/awt/Toolkit.java: s/gnu.java.awt.peer.gtk.GtkToolkit/gnu.awt.gtk.GtkToolkit/ and typo fixed. From-SVN: r57187
This commit is contained in:
parent
b423e6fe61
commit
cf0f53eb6e
8 changed files with 46 additions and 26 deletions
|
@ -42,7 +42,7 @@ package java.lang;
|
|||
* An assertion error normally occurs as a result of the <code>assert</code>
|
||||
* statement added in JDK 1.4, to indicate that an assertion failed. There
|
||||
* are enough constructors to ensure that
|
||||
* <code>new AssertionError(<em>expression</em)</code> will work for all
|
||||
* <code>new AssertionError(<em>expression</em>)</code> will work for all
|
||||
* espressions, regardless of type, as if the error message were given by
|
||||
* the string <code>"" + <em>expression</em></code>. This extends Error,
|
||||
* because you usually do not want to inadvertently trap an assertion failure.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue