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=2639

*** shadow/2639 Wed Jul 25 11:20:42 2001
--- shadow/2639.tmp.11217       Wed Jul 25 23:32:13 2001
***************
*** 2,9 ****
  | IndexOutOfBoundsException                                                  |
  +----------------------------------------------------------------------------+
  |        Bug #: 2639                        Product: XalanJ2                 |
! |       Status: NEW                         Version: 2.2.x                   |
! |   Resolution:                            Platform: PC                      |
  |     Severity: Blocker                  OS/Version: Windows NT/2K           |
  |     Priority: Other                     Component: Xalan                   |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | IndexOutOfBoundsException                                                  |
  +----------------------------------------------------------------------------+
  |        Bug #: 2639                        Product: XalanJ2                 |
! |       Status: RESOLVED                    Version: 2.2.x                   |
! |   Resolution: FIXED                      Platform: PC                      |
  |     Severity: Blocker                  OS/Version: Windows NT/2K           |
  |     Priority: Other                     Component: Xalan                   |
  +----------------------------------------------------------------------------+
***************
*** 164,166 ****
--- 164,174 ----
  equivalent to 3*x ... this is a standard-issue trick in
  performance-critical code. Possibly the compiler even
  optimizes 3*x to this anyway.
+ 
+ 
+ ------- Additional Comments From [EMAIL PROTECTED]  2001-07-25 23:32 -------
+ Committed WriterToUTF8Buffered.java, revision 1.3 to correct this bug.  In the 
+ end, I adopted a modified approach since I realized that the "if" test shown 
+ earlier would be executed every time through the loop in two of the write() 
+ methods.  Coupled with Gunnlaugur Thor Briem's trick, for which I am grateful, 
+ those methods use the multiply by three method.

Reply via email to