otp.git/lib/jinterface/java_src/com/ericsson/otp/erlang/OtpErlangString.java, branch OTP_R16B03

Update copyright years

2012-03-30T12:46:02+00:00

Merge branch 'vd/java-string-bug' into maint

2012-02-16T11:20:49+00:00

* vd/java-string-bug:
  add test for Java string bug
  workaround for Java bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6242664

OTP-9927

Update copyright years

2011-12-09T15:22:23+00:00

workaround for Java bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6242664

2011-11-24T09:22:57+00:00

Java 1.5 has a bug where detecting codepoint offsets in strings that are
created by String.substring() gives wrong results. The new implementation
uses a different method, avoinding the issue.

The following code will crash without the fix:
        final String s = "abcdefg";
        final String ss = s.substring(3, 6);
        final int[] cps = OtpErlangString.stringToCodePoints(ss);

Allow noncharacter code points in unicode encoding and decoding

2011-10-13T12:16:00+00:00

The two noncharacter code points 16#FFFE and 16#FFFF were not
allowed to be encoded or decoded using the unicode module or
bit syntax. That causes an inconsistency, since the noncharacters
16#FDD0 to 16#FDEF could be encoded/decoded.

There is two ways to fix that inconsistency.

We have chosen to allow 16#FFFE and 16#FFFF to be encoded and
decoded, because the noncharacters could be useful internally
within an application and it will make encoding and decoding
slightly faster.

Reported-by: Alisdair Sullivan

The R13B03 release.

2009-11-20T14:54:40+00:00