[#64210] Asking for clarification for exception handling usage — Rodrigo Rosenfeld Rosas <rr.rosas@...>
I've created a ticket for that but didn't get any feedback so I decided
5 messages
2014/08/05
[#64517] Fw: Re: Ruby and Rails to become Apache Incubator Project — Tetsuya Kitahata <[email protected]>
What do you think? >> Ruby developers
13 messages
2014/08/23
[#64524] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Henry Maddocks <hmaddocks@...>
2014/08/24
[#64525] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Brandon Weaver <keystonelemur@...>
2014/08/24
What benefits are there to this? I have a feeling that adding unnecessary
[#64526] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Tetsuya Kitahata <[email protected]>
2014/08/24
On Sat, 23 Aug 2014 22:43:46 -0700
[#64527] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Urabe Shyouhei <shyouhei@...>
2014/08/24
Here I am a Japanese. Before moving anywhere else answer to our question first: what benefits?
[#64528] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Tetsuya Kitahata <[email protected]>
2014/08/24
tax issue with each other.
[#64614] cowspace (work-in-progress) — Eric Wong <normalperson@...>
Hi all, I started working on a cowspace branch. Based on the mspace API
4 messages
2014/08/28
[#64615] [ruby-trunk - Feature #10181] [Open] New method File.openat() — oss-ruby-lang@...
Issue #10181 has been reported by Technorama Ltd..
10 messages
2014/08/28
[#64616] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Eric Wong <normalperson@...>
2014/08/28
I like this feature.
[#64623] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Joel VanderWerf <joelvanderwerf@...>
2014/08/29
On 08/28/2014 02:53 PM, Eric Wong wrote:
[#64634] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Eric Wong <normalperson@...>
2014/08/29
Joel VanderWerf <[email protected]> wrote:
[#64635] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Joel VanderWerf <joelvanderwerf@...>
2014/08/29
On 08/29/2014 12:55 AM, Eric Wong wrote:
[#64638] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Eric Wong <normalperson@...>
2014/08/29
Joel VanderWerf <[email protected]> wrote:
[#64627] [ruby-trunk - Feature #10182] [PATCH] string.c: move frozen_strings table to rb_vm_t — ko1@...
Issue #10182 has been updated by Koichi Sasada.
3 messages
2014/08/29
[#64671] Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...>
Why this fix solve your problem?
9 messages
2014/08/30
[#64672] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— SASADA Koichi <ko1@...>
2014/08/30
(2014/08/30 8:50), SASADA Koichi wrote:
[#64676] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— Eric Wong <normalperson@...>
2014/08/30
SASADA Koichi <[email protected]> wrote:
[#64684] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— Eric Wong <normalperson@...>
2014/08/31
Eric Wong <[email protected]> wrote:
[#64692] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— SASADA Koichi <ko1@...>
2014/08/31
(2014/08/31 0:18), Eric Wong wrote:
[ruby-core:64284] [ruby-trunk - Bug #10120] [Open] TestSprintf#test_float still an issue
From:
v.ondruch@...
Date:
2014-08-09 10:02:07 UTC
List:
ruby-core #64284
Issue #10120 has been reported by Vit Ondruch. ---------------------------------------- Bug #10120: TestSprintf#test_float still an issue https://bugs.ruby-lang.org/issues/10120 * Author: Vit Ondruch * Status: Open * Priority: Normal * Assignee: * Category: * Target version: * ruby -v: ruby 2.0.0p353 (2013-11-22 revision 43784) [i686-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- The fix for #8358 is build time solution. Unfortunately it turns out that this does not work so well for for distributions such as Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1101811 The issues is that the SSE2 support is determined during build time, i.e. if builder supports SSE2, then the instructions are enabled. However, later when the packaged Ruby is executed on platform which does not support SSE2, it may result in issues as described in the above mentioned ticket. Is there some way, how to resolve this issue in runtime rather than build time? -- https://bugs.ruby-lang.org/