Bug #3224
closedRegexp.new("...", nil, "n") is not documented
Description
=begin
While fixing the error messages for the number of parameters ( r27558 ), I noticed that Regexp.new accepts a third undocumented parameter.
Is it supported? If so it should be documented.
I also note that test_regexp.rb tests for the third parameter being "u", even though this has no effect. Maybe these tests should be removed?
=end
Updated by shyouhei (Shyouhei Urabe) over 14 years ago
=begin
That third argument to Regexp.new was effective in 1.8, but no longer in 1.9. I'm not sure if that situation should be called supported.
=end
Updated by mame (Yusuke Endoh) over 14 years ago
- Assignee set to marcandre (Marc-Andre Lafortune)
=begin
Hi,
As Shyouhei said, the argument is ignored. It left just for 1.8
compatibility.
Could you please add the fact into rdoc of Regexp#new and close
this ticket?
--
Yusuke Endoh mame@tsg.ne.jp
=end
Updated by naruse (Yui NARUSE) over 14 years ago
=begin
3rd argument "n" and //n sets the regexp to NONE flag.
Regexp.new("aa", nil, "n") =~ "\u3042aa"
(irb):11: warning: regexp match /.../n against to UTF-8 string
=end
Updated by naruse (Yui NARUSE) over 14 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
=begin
This issue was solved with changeset r27738.
Marc-Andre, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
=end