[#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:35274] [Ruby 1.9-Bug#4359][Rejected] regular expressions created with Regexp::FIXEDENCODING have incorrect inspect

From: Yui NARUSE <redmine@...>
Date: 2011-02-17 05:13:47 UTC
List: ruby-core #35274
Issue #4359 has been updated by Yui NARUSE.

Status changed from Feedback to Rejected

> I suppose I could add a special case, but that seems strange.  It also
> seems strange that inspect will not allow us to differentiate between
> regular expressions with different options.

inspect shows only essential information and for human readings.
The usage for machine processing is wrong way.
(The practical problem is Regexp#inspect provides the output like a regexp literal but there is no general syntax for fixed_encoding)

What is Object#inspect is arguable point but I think it is what provides the output for p method or irb.
see also http://redmine.ruby-lang.org/issues/show/735
----------------------------------------
http://redmine.ruby-lang.org/issues/show/4359

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

In This Thread

Prev Next