On Feb 22, 2013, at 11:33 AM, Brian Burkhalter wrote: >> Sweet. Just be aware that the floatValue() optimization requires >> Float.parseFloat to be fixed to match IEEE 754 behavior, as you're >> apparently doing with Double.parseDouble, to pass tests. > > Actually I missed that until yesterday but found it out myself. I do not > think however that the patch for 7131192 necessarily has to precede the fix > for 7192954, as long as the latter gets into the same release.
Oops, I had that reversed: I don't know that the patch for 7192954 has to precede that for 7131192 if the latter is deemed correct. B.
