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

  • Home
  • SEARCH
  • 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 6246315
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T12:39:57+00:00 2026-05-24T12:39:57+00:00

Two cases: ruby-1.9.2-p180 > puts {}.class => NilClass and ruby-1.9.2-p180 > puts a.class String

  • 0

Two cases:

ruby-1.9.2-p180 > puts {}.class

 => NilClass

and

ruby-1.9.2-p180 > puts "a".class
String
 => nil

It looks like puts {}.class is equivalent to (puts {}).class and puts "a".class is equivalent to puts ("a".class). Why is it so?

  • 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-24T12:39:58+00:00Added an answer on May 24, 2026 at 12:39 pm

    It’s treating {} as a block, not as a hash. RubyInside says so, and also shows how you can prove it using Ripper.

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

Sidebar

Related Questions

I would like to edit matlab scripts in two cases (1) In matlab Command
I am trying to extract some words from a string. The two cases look
I want to have two cases the same effect in ruby Hash, one is
I have two cases to match: either # ... ([0-9]+,[0-9]+) € ... # or #
For example if I have an Enum with two cases, does it make take
I have a question about the singleton pattern. I saw two cases concerning the
I'm messing around in Ruby some more. I have a file containing a class
If I create two String instances with the same content separately they are identical.
ruby has some edge cases which is hard to explain because parsing brings some
I'm doing a program and I would like to output a menu with two

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.