FAQ: Blocks, Procs, and Lambdas - Call Me Maybe


This community-built FAQ covers the “Call Me Maybe” exercise from the lesson “Blocks, Procs, and Lambdas”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Learn Ruby

FAQs on the exercise Call Me Maybe

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

Can someone help me understand the scenarios in which calling a proc would be preferable to defining a method? For example:

hi = Proc.new { puts "Hello!" }

def hello
  puts "Hello!"

Is calling a proc more memory efficient?

Same question.

I can’t seem to see how procs are any different from a method. Both are named/saved blocks of code functioning like an object, aren’t they?

It seems JavaScript doesn’t make any difference between the two, why does Ruby?