Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 738545
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T07:50:56+00:00 2026-05-14T07:50:56+00:00

I have the following code: #!/usr/bin/ruby class Person def self.speak p = self.new puts

  • 0

I have the following code:

#!/usr/bin/ruby

class Person
  def self.speak
    p = self.new
    puts "Hello"
    p.chatter
  end

private

  def chatter
    puts "Chattering"
  end
end

p = Person.new
Person.speak

I’d like to make chatter private, accessible only within p.. but I want p to be able to access it within the class method. Is there a better way to design this so chatter isn’t available to the public, but a “factory” method like self.speak can call chatter?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T07:50:56+00:00Added an answer on May 14, 2026 at 7:50 am

    In Ruby 1.8.7, “send” bypasses the usual protections against calling private methods:

    #!/usr/bin/ruby1.8
    
    class Person
    
      def self.speak
        puts "Hello"
        new.send(:chatter)
      end
    
      def speak
        puts "Hello"
        puts chatter
      end
    
      private
    
      def chatter
        puts "Chattering"
      end
    
    end
    
    Person.speak        # => Hello
                        # => Chattering
    Person.new.speak    # => Hello
                        # => Chattering
    

    However, what you want can be achieved without any voodoo, by simply having the class method do all the work, and the instance method defer to the class method:

    class Person
    
      def self.speak
        puts "Hello"
        puts "Chatter"
      end
    
      def speak
        self.class.speak
      end
    
    end
    

    If you had more than a few of these forwarding methods, it might be convenient to make a helper method that makes them for you:

    module DelegateToClass
    
      def delegate_to_class(name)
        define_method(name) do |*args|
          self.class.send(name, *args)
        end
      end
    
    end
    
    class Person
    
      extend DelegateToClass
    
      def self.speak
        puts "Hello"
        puts "Chatter"
      end
      delegate_to_class :speak
    
    end
    

    The built-in module Forwardable can do this just as well:

    require 'forwardable'
    
    class Person
    
      extend Forwardable
    
      def self.speak
        puts "Hello"
        puts "Chatter"
      end
    
      def_delegator self, :speak
    
    end
    

    def_delegator also bypasses protections against private methods.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 397k
  • Answers 397k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer I think you can do the following... select a project… May 15, 2026 at 3:17 am
  • Editorial Team
    Editorial Team added an answer I regularly use all manner of provider stacks with great… May 15, 2026 at 3:17 am
  • Editorial Team
    Editorial Team added an answer I posted earlier, but found out it didn't resolve your… May 15, 2026 at 3:17 am

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.