Forum: Ruby-core Refining methods that should be private

5cf8f058a4c094bb708174fb43e7a387?d=identicon&s=25 unknown (Guest)
on 2014-02-14 05:19
(Received via mailing list)
Issue #9452 has been updated by Tomoyuki Chikanaga.

Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN to
1.9.3: DONTNEED, 2.0.0: REQUIRED, 2.1: REQUIRED

----------------------------------------
Bug #9452: Refining methods that should be private
https://bugs.ruby-lang.org/issues/9452#change-45119

* Author: Jan Lelis
* Status: Closed
* Priority: Normal
* Assignee: Shugo Maeda
* Category:
* Target version:
* ruby -v: ruby 2.2.0dev (2014-01-25 trunk 44707) [x86_64-linux]
* Backport: 1.9.3: DONTNEED, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
Are refinements also meant to add private methods? This is what I tried:

    module R
      refine Object do
        def m
          puts "Success!"
        end

        private(:m)
      end
    end

    using R

    m # success
    42.m # success (= not private)


However, I can get near the desired functionality by defining a private
method first:

    class Object
      private
      def m
      end
    end

    module R
      refine Object do
        def m
          puts "Success!"
        end
      end
    end

    using R
    m # success
    42.m # no success (= it is private)

It calls the right code. But requires global core ext.
This topic is locked and can not be replied to.