[#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:35179] [Ruby 1.9-Bug#4386][Feedback] encoding: directive does not affect regex expressions

From: Usaku NAKAMURA <redmine@...>
Date: 2011-02-10 00:47:25 UTC
List: ruby-core #35179
Issue #4386 has been updated by Usaku NAKAMURA.

Status changed from Rejected to Feedback

IMHO, the US-ASCII fallback of regexp literals is a spec bug of ruby.
The encoding of regexp literals should be the same as script encoding, like string literals.

But, as Eric said, US-ASCII regexp can match with UTF-8 string.
So, this bug may not cause any troubles, I guess.

If the problem has occurred concretely something, please give the example.
Not so, make this ticket to feature request, because changing this behavior
may causes some compatibility problem.

----------------------------------------
http://redmine.ruby-lang.org/issues/show/4386

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

In This Thread