Project

General

Profile

Bug #9623

warning: "named capture conflicts a local variable" does not allow loops with named captures

Added by Eric Hodel over 2 years ago.

Status:
Open
Priority:
Normal
Assignee:
-
ruby -v:
ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin13.0]
[ruby-core:61423]

Description

Given the following example:

args = []

remaining = 'a,b,c'

begin
  /(?<token>[^,]*),?(?<remaining>.*)/ =~ remaining

  args << token
end until remaining.empty?

p args

Gives a warning with -w: test.rb:6: warning: named capture conflicts a local variable - remaining

I'm unsure if the warning is useful here. Reassigning in the loop through the named captures seems clearer than using the regexp globals.


Related issues

Related to Ruby trunk - Bug #12359: Named captures "conflict" warning is unnecessary and limits uses of named captures Closed

History

#1 Updated by Benoit Daloze 4 months ago

  • Related to Bug #12359: Named captures "conflict" warning is unnecessary and limits uses of named captures added

Also available in: Atom PDF