ruby-dev (Japanese) list archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-dev:52059]  [Ruby master Bug#10436] ruby -c and ripper inconsistency: m(&nil) {}
       [not found] <redmine.issue-10436.20141028012456.271@ruby-lang.org>
@ 2023-11-13 19:41 ` jemmai (Jemma Issroff) via ruby-dev
  2024-02-20 12:01 ` [ruby-dev:52068] " yui-knk (Kaneko Yuichiro) via ruby-dev
  1 sibling, 0 replies; 2+ messages in thread
From: jemmai (Jemma Issroff) via ruby-dev @ 2023-11-13 19:41 UTC (permalink / raw
  To: ruby-dev; +Cc: jemmai (Jemma Issroff)

Issue #10436 has been updated by jemmai (Jemma Issroff).


This bug still exists on Ripper. Should we try revive @jeremyevans0's patch?

It is potentially worth noting that Prism creates a `ParseError`: "Multiple block arguments; only one block is allowed"

----------------------------------------
Bug #10436: ruby -c and ripper inconsistency: m(&nil) {}
https://bugs.ruby-lang.org/issues/10436#change-105301

* Author: akr (Akira Tanaka)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.2.0dev (2014-10-27 trunk 48168) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
m(&nil) {} というまちがったコードは
ruby -c でちゃんとエラーになるのに、
Ripper.sexp ではならないようです。

```
% cat z.rb 
m(&nil) {}
% ruby -c z.rb 
z.rb:1: both block arg and actual block given
% ruby -rripper -e 'p Ripper.sexp(STDIN.read)' < z.rb
[:program, [[:method_add_block, [:method_add_arg, [:fcall, [:@ident, "m", [1, 0]]], [:arg_paren, [:args_add_block, [], [:var_ref, [:@kw, "nil", [1, 3]]]]]], [:brace_block, nil, [[:void_stmt]]]]]]
% ruby -v
ruby 2.2.0dev (2014-10-27 trunk 48168) [x86_64-linux]
```


---Files--------------------------------
ripper-block_dup_check-10436.patch (2.2 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [ruby-dev:52068]  [Ruby master Bug#10436] ruby -c and ripper inconsistency: m(&nil) {}
       [not found] <redmine.issue-10436.20141028012456.271@ruby-lang.org>
  2023-11-13 19:41 ` [ruby-dev:52059] [Ruby master Bug#10436] ruby -c and ripper inconsistency: m(&nil) {} jemmai (Jemma Issroff) via ruby-dev
@ 2024-02-20 12:01 ` yui-knk (Kaneko Yuichiro) via ruby-dev
  1 sibling, 0 replies; 2+ messages in thread
From: yui-knk (Kaneko Yuichiro) via ruby-dev @ 2024-02-20 12:01 UTC (permalink / raw
  To: ruby-dev; +Cc: yui-knk (Kaneko Yuichiro)

Issue #10436 has been updated by yui-knk (Kaneko Yuichiro).

Status changed from Open to Closed

This is solved by https://bugs.ruby-lang.org/issues/20257 (https://github.com/ruby/ruby/pull/9923).

----------------------------------------
Bug #10436: ruby -c and ripper inconsistency: m(&nil) {}
https://bugs.ruby-lang.org/issues/10436#change-106914

* Author: akr (Akira Tanaka)
* Status: Closed
* Priority: Normal
* ruby -v: ruby 2.2.0dev (2014-10-27 trunk 48168) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
m(&nil) {} というまちがったコードは
ruby -c でちゃんとエラーになるのに、
Ripper.sexp ではならないようです。

```
% cat z.rb 
m(&nil) {}
% ruby -c z.rb 
z.rb:1: both block arg and actual block given
% ruby -rripper -e 'p Ripper.sexp(STDIN.read)' < z.rb
[:program, [[:method_add_block, [:method_add_arg, [:fcall, [:@ident, "m", [1, 0]]], [:arg_paren, [:args_add_block, [], [:var_ref, [:@kw, "nil", [1, 3]]]]]], [:brace_block, nil, [[:void_stmt]]]]]]
% ruby -v
ruby 2.2.0dev (2014-10-27 trunk 48168) [x86_64-linux]
```


---Files--------------------------------
ripper-block_dup_check-10436.patch (2.2 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-02-20 12:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <redmine.issue-10436.20141028012456.271@ruby-lang.org>
2023-11-13 19:41 ` [ruby-dev:52059] [Ruby master Bug#10436] ruby -c and ripper inconsistency: m(&nil) {} jemmai (Jemma Issroff) via ruby-dev
2024-02-20 12:01 ` [ruby-dev:52068] " yui-knk (Kaneko Yuichiro) via ruby-dev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).