Bug #12669: syntax error at assinments of command

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN

[nobu (Nobuyoshi Nakada)]

Related to #12402, I found other kind inconsistencies.

simple assignment and op assign of command cause syntax error,
while simple assignments don't.

$ ruby -ce 'a = b = raise "x"'
Syntax OK

$ ruby -ce 'a = b += raise "x"'
-e:1: syntax error, unexpected tSTRING_BEG, expecting keyword_do or '{' or '('
a = b += raise "x"
                ^

$ ruby -ce 'a += b = raise "x"'
-e:1: syntax error, unexpected tSTRING_BEG, expecting keyword_do or '{' or '('
a += b = raise "x"
                ^

$ ruby -ce 'a += b += raise "x"'
-e:1: syntax error, unexpected tSTRING_BEG, expecting keyword_do or '{' or '('
a += b += raise "x"
                 ^

https://github.com/ruby/ruby/compare/trunk...nobu:chained-rhs

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset r55888.

---

parse.y: chained assignments

• parse.y (command_asgn, arg): fix syntax errors with chained
  assignment with op assign. [Bug #12669]

[whitequark (whitequark *)]

Will this change be backported?