[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35121] [Ruby 1.9-Feature#4197] Improvement of the benchmark library

From: Benoit Daloze <redmine@...>
Date: 2011-02-06 16:33:59 UTC
List: ruby-core #35121
Issue #4197 has been updated by Benoit Daloze.


Hi,
On 6 February 2011 03:07, Nobuyoshi Nakada wrote:
> Hi,
>
> A library should not leave such globally shared states changed.

I know, that is why I prefer to use IO#flush in libraries.

> `ensure' clause does not affect the return value.
> So tap trick is not needed here.

My mistake, I did not know `ensure' clause preserve the return value.
That's definitely handful.

I guess then the patch is fine.

Tomoyuki: Please commit it (if you want), that will clean that part until I work on it.

>> On IO#sync's subject, I thought once it would be nice to have a block form of IO#sync, which could use ensure.
>
> It's another story, please file new ticket.

I now think it is not a good idea, giving it is probably best not to use IO#sync in a library.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/4197

----------------------------------------
http://redmine.ruby-lang.org

In This Thread

Prev Next