Mark,
in comparison to the other JEPs proposed recently, this seems quite
vague. There is a brief list of candidate collections nestled in the
very middle of the JEP, but that's it. Given that the alternative
collection libraries have existed for many years, it seems to me the
author has enough
Omair Majid wrote:
Yes, I am a little afraid of the disruption too, which is why I
proposed it for jdk8, not for a 7 update.
That said, I think these directories should be visible by default. We
are storing preferences in it and hiding the directory from the
sysadmin serves no purpose. In
Hi,
Am 29.09.2011 05:27, schrieb Xueming Shen:
Hi,
On 9/28/2011 3:44 PM, Ulf Zibis wrote
3. Consider additionally 6795537 - UTF_8$Decoder returns wrong results
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6795537
(1) new byte[]{(byte)0xE1, (byte)0x80, (byte)0x42} ---
Am 28.09.2011 06:36, schrieb Sebastian Sickelmann:
Am 27.09.2011 17:38, schrieb Sean Mullan:
On 9/24/11 5:55 AM, Sebastian Sickelmann wrote:
Am 23.09.2011 20:54, schrieb Sean Mullan:
On 9/17/11 3:09 PM, Sebastian Sickelmann wrote:
i have updated the webrev [0].
But i think that L69 and L72
Has anyone seen this testcase fail like this?
FAILED: java/nio/channels/FileChannel/Transfers.java
ACTION: main -- Failed. Execution failed: `main' threw exception:
java.lang.RuntimeException: Some tests failed
REASON: Assumed action based on file name: run main Transfers
TIME: 3.337 seconds
2011/9/29 23:13 -0700, pdoubl...@gmail.com:
Mark,
in comparison to the other JEPs proposed recently, this seems quite
vague. There is a brief list of candidate collections nestled in the
very middle of the JEP, but that's it. Given that the alternative
collection libraries have existed for
Hello.
Please review this patch to add CheckedQueue to Collections. Test case
provided.
Webrev at: http://cr.openjdk.java.net/~mduigou/4533691/0/webrev/
Thanks,
Darryl
On 09/30/2011 07:09 AM, Ulf Zibis wrote:
(1) new byte[]{(byte)0xE1, (byte)0x80, (byte)0x42} ---
CoderResult.malformedForLength(1)
It appears the Unicode Standard now explicitly recommends to return
the malformed length 2,
what UTF-8 is doing now, for this scenario
My idea behind is, that
Kelly O'Hair wrote:
Has anyone seen this testcase fail like this?
FAILED: java/nio/channels/FileChannel/Transfers.java
ACTION: main -- Failed. Execution failed: `main' threw exception:
java.lang.RuntimeException: Some tests failed
REASON: Assumed action based on file name: run main Transfers
