From: manga.osyo@... Date: 2020-12-08T14:09:38+00:00 Subject: [ruby-core:101316] [Ruby master Bug#17377] A warning message doesn't display using -W option on irb Issue #17377 has been updated by osyo (manga osyo). Thanks issues :) There was no warning message in Ruby 3.0.0.0dev either. ```ruby ~ $ irb -W irb(main):001:0> RUBY_DESCRIPTION => "ruby 3.0.0dev (2020-12-08T10:37:42Z master 09229c71bc) [x86_64-linux]" irb(main):002:0> IRB::VERSION => "1.2.7" irb(main):003:0> Object.tainted? => false irb(main):004:0> ``` ---------------------------------------- Bug #17377: A warning message doesn't display using -W option on irb https://bugs.ruby-lang.org/issues/17377#change-89009 * Author: ima1zumi (Mari Imaizumi) * Status: Open * Priority: Normal * ruby -v: ruby 3.0.0preview1 (2020-09-25 master 0096d2b895) [x86_64-darwin19] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- ## Expected Using -W option, a warning statement display when deprecated method call. ``` $ irb -W irb(main):001:0> Object.tainted? (irb):1: warning: Object#tainted? is deprecated and will be removed in Ruby 3.2 => false ``` ## Actual Although using -W option, a warning statement doesn't display when deprecated method call. ``` ~/development/sandbox $ ruby -v ruby 3.0.0preview1 (2020-09-25 master 0096d2b895) [x86_64-darwin19] ~/development/sandbox $ irb -v irb 1.2.7 (2020-09-19) ~/development/sandbox $ irb -W irb(main):001:0> Object.tainted? => false ``` -- https://bugs.ruby-lang.org/ Unsubscribe: