FAQ: Blocks, Procs, and Lambdas - Passing Your Proc to a Method

This community-built FAQ covers the “Passing Your Proc to a Method” 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 Passing Your Proc to a Method

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!

I’m trying to understand how a Proc is useful vs. a Method… was able to succesfully pass the proc to a method see image 1… but for image 2 was wondering how to replace the same process without the Proc… seems I am missing something that is obvious…



Line 4 is not a Proc. See line 4 in your previous post.

Like function expressions in JavaScript, we can reassign a new Proc to the variable anytime we wish to alter the code, and do it on the fly. With a defined method we don’t have that luxury. It would mean having to create multiple methods to accomodate our needs and that cannot be done when the program is running.