[ http://issues.apache.org/jira/browse/HARMONY-103?page=all ]
Nathan Beyer updated HARMONY-103:
---------------------------------
Attachment: StringBuilderTest.java
JUnit test case for StringBuilder. I've run this test against Sun's JRE 5.0_5
and BEA's JRE 5.0_4_R26.0 and this test passes with one exception with the
"insert(int, char)" method, which based on the API specification I would
consider a bug, but how this is handled in Harmony is up for debate.
Note: I was unable to test the serialization, as from what I can tell the
current Harmony snapshots don't support it. I was getting a NoSuchAlgorithm for
the MesageDigest SHA. However, I do believe the the serialization is
implemented correctly, at least according to the specification.
> java.lang.StringBuilder Implementation for LUNI
> -----------------------------------------------
>
> Key: HARMONY-103
> URL: http://issues.apache.org/jira/browse/HARMONY-103
> Project: Harmony
> Type: New Feature
> Components: Classlib
> Reporter: Nathan Beyer
> Attachments: StringBuilder.java, StringBuilderTest.java
>
> This bug is for submitting an implementation of the java.lang.StringBuilder
> to the LUNI module of classlib. The implementation and class definition is
> based on the specification at
> http://java.sun.com/j2se/1.5.0/docs/api/java/lang/StringBuilder.html.
> The implementation is not complete, there are a few method that are either
> incomplete or not implemented. All of these are related to the Unicode Code
> Point support, as defined by Java 5. As for the rest of the implementation,
> there are probably a number of optimization points, but the focus was to
> complete the functionality and make it compatible with various Java 5
> runtimes.
> Additionally, I had a problem with compiling this class in Eclipse 3.1.2.
> When I set the compiler to Java 1.4 compliance level, the methods which
> implement the Appendable interface cause compilation errors. When I set the
> compiler to Java 5.0 compliance with Java 1.4 .class file compatability and
> Java 1.4 source compatibility, the class compiled fine. I'm not sure if this
> is quirk of the JDT compiler or what, but I'm going to do some investigation
> and testing to see if I can isolate it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
