Re: Why doesn't Channels.newChannel(OutputStream) flush?

2021-04-06 Thread Charles Oliver Nutter
fter the write loop. > > Brian > > On Apr 6, 2021, at 12:30 PM, Charles Oliver Nutter > wrote: > > While debugging some subprocess logic in JRuby today I came to the > realization that the WritableByteChannel returned by > Channels.newChannel(OutputStream) is "

Why doesn't Channels.newChannel(OutputStream) flush?

2021-04-06 Thread Charles Oliver Nutter
While debugging some subprocess logic in JRuby today I came to the realization that the WritableByteChannel returned by Channels.newChannel(OutputStream) is "broken". https://github.com/jruby/jruby/pull/6649/commits/5a6912caf3adb70fb4c210c73ae02fbf16f404d9 The issue arises when the provided

URLClassLoader poisons the global JarFile cache

2020-06-05 Thread Charles Oliver Nutter
Hey folks, with some help from Claes Redestad I've filed an issue with analysis and reproduction of the legendary "zip file closed" error. https://bugs.openjdk.java.net/browse/JDK-8246714 It turns out that URLClassLoader is just plain broken when used to access jar files (which means this bug

Re: ISO-8859-16 charset/decoder/encoder

2017-08-25 Thread Charles Oliver Nutter
Thanks everyone, I'll work with Sherman to get a patch together. On Fri, Aug 25, 2017 at 1:19 PM Naoto Sato wrote: > Yep, I believe Sherman is more knowledgeable on this than me :-) > > Naoto > > On 8/25/17 9:30 AM, Alan Bateman wrote: > > > > > > On 25/08/2017 17:19,

Re: ISO-8859-16 charset/decoder/encoder

2017-08-24 Thread Charles Oliver Nutter
Finally got around to opening an issue for this. https://bugs.openjdk.java.net/browse/JDK-8186751 I'm happy to do the requisite work to bring this patch to fruition, but since this is my first patch I'm not sure of the process. - Charlie On Fri, Nov 22, 2013 at 5:06 AM Charles Oliver Nutter

Re: JEP 254: Compact Strings - length limits

2016-09-06 Thread Charles Oliver Nutter
On Tue, Sep 6, 2016 at 1:04 PM, Xueming Shen wrote: > Yes, it's a known "limit" given the nature of the approach. It is not > considered > to be an "incompatible change", because the max length the String class > and > the corresponding buffer/builder classes can

Re: Expecting Integer.valueOf(String) to accept Literal format ...

2016-04-09 Thread Charles Oliver Nutter
gt; such things, they can front this API by replacing underscores themselves, > or more generally have something else accept underscores and canonicalize > to what Integer.valueOf expects. > > On Saturday, April 9, 2016, Charles Oliver Nutter <head...@headius.com> > wrot

Re: Expecting Integer.valueOf(String) to accept Literal format ...

2016-04-09 Thread Charles Oliver Nutter
I feel like this is an obvious API gap that should be fixed. If it is a valid syntax in javac, it should be a valid syntax in JDK APIs. My first impression was that this was an obvious oversight. - Charlie (mobile) On Apr 9, 2016 21:04, "Christoph Engelbert" wrote: > Hey

Re: Loopy CallSite

2014-07-12 Thread Charles Oliver Nutter
I played with this some years ago. Doesn't it just become recursive, because it won't inline through the dynamicInvoker? - Charlie (mobile) On Jul 12, 2014 9:36 AM, Remi Forax fo...@univ-mlv.fr wrote: It seems that the JIT is lost with whe there is a loopy callsite and never stabilize (or the

Re: Different error decoding Shift-JIS sequence in JDK8

2013-11-28 Thread Charles Oliver Nutter
11:02, Charles Oliver Nutter wrote: Apologies if this is not the correct place to post this, bit i18n seemed more focused on languages and localization than the mechanics of transcoding. I have noticed a behavioral difference in JDK8 decoding a two-byte Shift-JIS sequence. Specifically, JDK8

Different error decoding Shift-JIS sequence in JDK8

2013-11-22 Thread Charles Oliver Nutter
Apologies if this is not the correct place to post this, bit i18n seemed more focused on languages and localization than the mechanics of transcoding. I have noticed a behavioral difference in JDK8 decoding a two-byte Shift-JIS sequence. Specifically, JDK8 appears to report malformed input for

ISO-8859-16 charset/decoder/encoder

2013-11-22 Thread Charles Oliver Nutter
Again, apologies if this is not the right list. OpenJDK does not currently contain support for encoding/decoding ISO-8859-16. A JRuby user recently reported that they needed this encoding. So, I implemented it. Here's a link to the charset/decoder/encoder in JRuby's repository:

Re: encoding-agnostic byte[]-based regexp engine...interested?

2007-11-19 Thread Charles Oliver Nutter
charlie hunt wrote: Hi Charlie, I'm adding OpenJDK's Java SE core libraries since that's where Java NIO lives. I doubt anything could be done at the class libraries level since an API addition / enhancement would likely require JCP activity. But, there may be some value in raising some