aboutsummaryrefslogtreecommitdiffstats
path: root/lib/jinterface/java_src/com/ericsson/otp/erlang/OtpErlangString.java
AgeCommit message (Collapse)Author
2014-11-25[jinterface] cleanup code according to new styleVlad Dumitrescu
2014-09-11remove warnings: @Override, switch fall-throughVlad Dumitrescu
2014-09-11make serialVersionUID fields privateVlad Dumitrescu
2014-09-11remove unnecessary Cloneable and SerializableVlad Dumitrescu
2014-06-08Fix a few javadoc errorsAnthony Ramine
Reported-by: Boris Mühmer
2012-03-30Update copyright yearsBjörn-Egil Dahlberg
2012-02-16Merge branch 'vd/java-string-bug' into maintHenrik Nord
* 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
2011-12-09Update copyright yearsBjörn-Egil Dahlberg
2011-11-24workaround for Java bug ↵Vlad Dumitrescu
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6242664 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);
2011-10-13Allow noncharacter code points in unicode encoding and decodingBjörn Gustavsson
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
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-22 18:35:13 +0000