Bug #16901: `-W:no-deprecated` does not stop some deprecated warnings

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
• Backport: 2.5: DONTNEED, 2.6: DONTNEED, 2.7: REQUIRED

[znz (Kazuhiro NISHIYAMA)]

$ ruby -v -W:no-deprecated -e 'IO.read(IO::NULL,{dummy:0})'
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
-e:1: warning: Using the last argument as keyword parameters is deprecated

I attach a draft patch for ruby_2_7 branch.
I don't know where declaration of rb_warn_deprecated should be.

[nobu (Nobuyoshi Nakada)]

znz (Kazuhiro NISHIYAMA) wrote:

I don't know where declaration of rb_warn_deprecated should be.

include/ruby/internal/error.h?

[nobu (Nobuyoshi Nakada)]

Sorry, it's for 2.7.
It should be in ruby/ruby.h, near rb_warn and so on.

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: REQUIRED

Thank you for the patch for 2.7. I will fill Backport field and close this ticket to be noticed as backport ticket.

[nagachika (Tomoyuki Chikanaga)]

• Status changed from Open to Closed

[znz (Kazuhiro NISHIYAMA)]

• File use-rb_warn_deprecated-instead-of-rb_warn-2.diff use-rb_warn_deprecated-instead-of-rb_warn-2.diff added