On 02/07/2014 01:42, Naoto Sato wrote:
I further modified the fix:
- Made sure the SharedSecret is lazily evaluated.
- Added the missing JavaAWTFontAccessImpl file
- Added a test case
http://cr.openjdk.java.net/~naoto/8038092/webrev.2/
Please review.
This looks much better.
I think the only case that need detailed examination now is whether it
is possible for SharedSecrets.getJavaAWTFontAccess to return null. I'm
thinking about the case where 2+ threads use Bidi for the first time, or
say something else initializes TextAttribute at the same time that
another thread uses Bidi for the first time.
Is the change to Bug7051769.java really needed?
-Alan