Prev: CentOS 5 and Ruby 1.9.1 - conflict with 1.8.6
Next: Conditional keys in hash - out of the box?
From: Robert Klemme on 7 Mar 2010 12:13
On 03/07/2010 01:09 PM, Alex DeCaria wrote:
> Should I submit a bug report, or do you think it will be eventually
> noticed on this forum?

I'd check whether that bug is known already and only file in cast it is not:
http://redmine.ruby-lang.org/projects/show/ruby-191

Kind regards

robert

--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
From: Caleb Clausen on 7 Mar 2010 12:16
On 3/7/10, Alex DeCaria <alex.decaria(a)millersville.edu> wrote:
> Should I submit a bug report, or do you think it will be eventually
> noticed on this forum?

File a bug.

From: Yukihiro Matsumoto on 13 Mar 2010 02:00
Hi,

In message "Re: Different behavior of '$,' output separator in Ruby 1.9"
on Sat, 6 Mar 2010 04:06:22 +0900, Alex DeCaria <alex.decaria(a)millersville.edu> writes:

|In switching to Ruby 1.9 from 1.8 I notice that the behavior of the '$,'
|output separator has changed. In Ruby 1.9 the output separator is
|placed after a newline character, but this didn't happen with Ruby 1.8.

Sorry it was a bug introduce in r11003. Fixed in r26906.

matz.

First  |  Prev  | 
Pages: 1 2
Prev: CentOS 5 and Ruby 1.9.1 - conflict with 1.8.6
Next: Conditional keys in hash - out of the box?