You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/08/01 15:48:26 UTC
[Bug 730] - NullPointerExceptions and ArrayIndexOutOfBoundsExceptions used for normal program control
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=730
*** shadow/730 Fri Jul 20 13:15:28 2001
--- shadow/730.tmp.22003 Wed Aug 1 06:48:26 2001
***************
*** 7,13 ****
| Severity: Normal OS/Version: All |
| Priority: High Component: Core |
+----------------------------------------------------------------------------+
! | Assigned To: xerces-j-dev@xml.apache.org |
| Reported By: jo2847@sbc.com |
+----------------------------------------------------------------------------+
| URL: |
--- 7,13 ----
| Severity: Normal OS/Version: All |
| Priority: High Component: Core |
+----------------------------------------------------------------------------+
! | Assigned To: zongaro@ca.ibm.com |
| Reported By: jo2847@sbc.com |
+----------------------------------------------------------------------------+
| URL: |
***************
*** 93,95 ****
--- 93,109 ----
fCharsOffset[chunk] = new int[INITIAL_CHUNK_SIZE];
return true;
}
+
+ ------- Additional Comments From zongaro@ca.ibm.com 2001-08-01 06:48 -------
+ I spoke with a JIT compiler developer on IBM's JDK's. He indicated that (at
+ least on IBM's JDK's), there were cases in which using try-catch could be more
+ efficient than using the logically equivalent if-else, if exceptions didn't get
+ thrown very often.
+
+ I've changed some instances in which if-else should be superior; in some cases
+ in which try-catch would be better, I've instead tried to reduce the number of
+ exceptions actually thrown, without increasing memory usage by too much.
+
+ The changes aren't complete, so I won't mark the bug as "FIXED", but I hope what
+ I've done thus far improves the situation. These changes are available in the
+ Xerces-J 1.4.2.
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org