[#71815] [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache — tenderlove@...
Issue #11768 has been reported by Aaron Patterson.
6 messages
2015/12/03
[#71819] Re: [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache
— Eric Wong <normalperson@...>
2015/12/03
[email protected] wrote:
[#71821] Re: [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache
— Aaron Patterson <tenderlove@...>
2015/12/03
On Thu, Dec 03, 2015 at 10:51:08PM +0000, Eric Wong wrote:
[#71824] Re: [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache
— Eric Wong <normalperson@...>
2015/12/04
Aaron Patterson <[email protected]> wrote:
[#71818] [Ruby trunk - Feature #11769] [Open] optimize case / when for `nil` — tenderlove@...
Issue #11769 has been reported by Aaron Patterson.
4 messages
2015/12/03
[#71825] Re: [Ruby trunk - Feature #11769] [Open] optimize case / when for `nil`
— Eric Wong <normalperson@...>
2015/12/04
[email protected] wrote:
[#71931] [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder — normalperson@...
Issue #11786 has been reported by Eric Wong.
9 messages
2015/12/08
[#71932] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— Eric Wong <normalperson@...>
2015/12/08
Oops, I forgot to free the table when iseq is destroyed :x
[#71934] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— SASADA Koichi <ko1@...>
2015/12/08
On 2015/12/08 12:43, Eric Wong wrote:
[#71936] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— Eric Wong <normalperson@...>
2015/12/08
SASADA Koichi <[email protected]> wrote:
[#71938] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— SASADA Koichi <ko1@...>
2015/12/08
On 2015/12/08 13:53, Eric Wong wrote:
[#72028] [Ruby trunk - Feature #11405] [Assigned] [PATCH] hash.c: minor speedups to int/fixnum keys — mame@...
Issue #11405 has been updated by Yusuke Endoh.
5 messages
2015/12/10
[#72040] Re: [Ruby trunk - Feature #11405] [Assigned] [PATCH] hash.c: minor speedups to int/fixnum keys
— Eric Wong <normalperson@...>
2015/12/10
[email protected] wrote:
[#72045] Ruby 2.3.0-preview2 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 2.3.0-preview2.
10 messages
2015/12/11
[#72047] Re: Ruby 2.3.0-preview2 Released
— SASADA Koichi <ko1@...>
2015/12/11
Please add your optimizations before RC1.
[#72054] Re: Ruby 2.3.0-preview2 Released
— Eric Wong <normalperson@...>
2015/12/11
SASADA Koichi <[email protected]> wrote:
[#72436] Re: Ruby 2.3.0-preview2 Released
— SASADA Koichi <ko1@...>
2015/12/22
On 2015/12/11 18:06, Eric Wong wrote:
[#72440] Re: Ruby 2.3.0-preview2 Released
— Eric Wong <normalperson@...>
2015/12/22
SASADA Koichi <[email protected]> wrote:
[#72069] [Ruby trunk - Feature #11405] [PATCH] hash.c: minor speedups to int/fixnum keys — mame@...
Issue #11405 has been updated by Yusuke Endoh.
3 messages
2015/12/12
[#72115] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US — "U.NAKAMURA" <usa@...>
Hi,
7 messages
2015/12/14
[#72124] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US
— Martin J. Dürst <duerst@...>
2015/12/14
On 2015/12/14 22:34, U.NAKAMURA wrote:
[#72125] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US
— "U.NAKAMURA" <usa@...>
2015/12/15
Hi,
[ruby-core:72124] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US
From:
Martin J. Dürst <duerst@...>
Date:
2015-12-14 23:39:26 UTC
List:
ruby-core #72124
On 2015/12/14 22:34, U.NAKAMURA wrote: > Hi, > > In message "[ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US" > on Mon, 14 Dec 2015 22:11:33 +0900 (JST), [email protected] wrote: >> * enc/ebcdic.h: new dummy encoding EBCDIC-US > > This is great! Thanks. I did it because somebody at the Ruby Kaigi party said that they needed it, and I had received code earlier that (almost) did it. > But I want to know where the name 'EBCDIC-US' came from. The name came from http://www.iana.org/assignments/character-sets/character-sets.xhtml, as MIB 2078. > I guess this is the encoding that is named as 'IBM037' by IANA, > and it's aliases are 'ebcdic-cp-us' and so on. Looking at http://tools.ietf.org/html/rfc1345, the code conversion is indeed much closer to ebcdic-cp-us than to EBCDIC-US. So using EBCDIC-US is definitely wrong. Thanks for pointing this out. We need some more careful checks, but it seems that the data that I used is the same as on https://en.wikipedia.org/wiki/EBCDIC_037, whereas 'IBM037' in http://tools.ietf.org/html/rfc1345 has the C2 area all unassigned. > I'n not against for 'EBCDIC-US'. > But, if we use this as the real name, we should explain the reason. We definitely need to fix this, most probably to make the name 'IBM037', and add some alias(es). I don't think we need all the aliases from IANA (cp037, ebcdic-cp-us, ebcdic-cp-ca, ebcdic-cp-wt, ebcdic-cp-nl, csIBM037), but I would like to have one alias with the famous 6 letters in it so that it's easier for people to find. I'd probably go with 'ebcdic-cp-us'. Any advice appreciated! The last time I have used EBCDIC was in the early 1980ies, so that's a long time ago. Regards, Martin.