Project

General

Profile

Bug #3224

Regexp.new("...", nil, "n") is not documented

Added by marcandre (Marc-Andre Lafortune) about 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Target version:
ruby -v:
ruby 1.9.2dev (2010-04-30 trunk 27554) [x86_64-darwin10.3.0]
Backport:
[ruby-core:29893]

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

History

#1

Updated by shyouhei (Shyouhei Urabe) about 9 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

#2

Updated by mame (Yusuke Endoh) about 9 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

#3

Updated by naruse (Yui NARUSE) about 9 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

#4

Updated by naruse (Yui NARUSE) about 9 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

Also available in: Atom PDF