uploading of new code

raffaello.giulietti at gmail.com raffaello.giulietti at gmail.com
Wed Apr 18 13:55:23 UTC 2018


in thread [1] I mention a clean room implementation of
Double.toString(double) and my willingness to contribute it to the
OpenJDK project to fix [2].

As of today, my code resides in a module that exports a package simply
named "math". The reason I do not alter the original OpenJDK
implementation is that I need it *along* my code to be able to compare
results. I developed the code in total ignorance of the OpenJDK
implementation, so to speak. This is not the end goal, of course, but
the safest way to review/test it without potentially breaking existing code.

As a consequence, I wonder how to best deliver my contribution to the
OpenJDK project in this phase. As far as I understand, webrev [3] is
better suited for *changes* to existing code, not specifically for *new*

I also understand that attachments are not recommended. On the other
hand, pasting some thousands of Java lines in a post on the mailing list
isn't practical either, I guess.

The code currently consists of about 8 files for a total of about 3000 +
600 lines for code + tests.

So, how can I best proceed with this initial delivery?


[2] https://bugs.openjdk.java.net/browse/JDK-4511638
[3] http://openjdk.java.net/guide/codeReview.html

More information about the core-libs-dev mailing list