[#75225] [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7) — k@...
Issue #12324 has been reported by Kazuki Yamaguchi.
6 messages
2016/04/27
[#78693] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
k@rhe.jp wrote:
[#78701] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Kazuki Yamaguchi <k@...>
2016/12/17
On Sat, Dec 17, 2016 at 01:31:12AM +0000, Eric Wong wrote:
[#78702] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
Kazuki Yamaguchi <k@rhe.jp> wrote:
[ruby-core:74920] [Ruby trunk Feature#12026][Closed] Support warning processor
From:
matz@...
Date:
2016-04-13 05:53:55 UTC
List:
ruby-core #74920
Issue #12026 has been updated by Yukihiro Matsumoto. Status changed from Open to Closed Hi, * I agree with the need for filtering/customizing warnings * but I disagree with the use of a global variable * casting warnings via `warn` method may work * but there might be need for controlling warnings per gem/class basis In summary, we cannot accept this proposal as it is. Matz. ---------------------------------------- Feature #12026: Support warning processor https://bugs.ruby-lang.org/issues/12026#change-58046 * Author: Jeremy Evans * Status: Closed * Priority: Normal * Assignee: ---------------------------------------- This adds a simple way to filter warnings from being displayed. You just set a $WARNING_FILTER with a regexp, and any warnings that match the regexp will not be displayed. I think this is a much simpler approach to filtering warnings than feature #11588, while allowing the same type of capability. This is backwards compatible, in that you can set $WARNING_FILTER in previous versions of ruby without problems. This should not cause any performance issues, as the regexp matching isn't done until the warning message is about to be displayed. It's possible to use something other than a global variable to store the warning filter, but a global variable was the easiest way to implement it, it has a global effect, and similar flags such as $VERBOSE are also global variables, so I think a global variable makes sense. ---Files-------------------------------- 0001-Support-warning-filters.patch (4.12 KB) 0001-Add-WARNING_PROCESSOR-for-processing-warnings.patch (5.13 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>