FAQ: Introduction to Ruby - Multi-Line Comments


This community-built FAQ covers the “Multi-Line Comments” exercise from the lesson “Introduction to Ruby”.

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

Learn Ruby

FAQs on the exercise Multi-Line Comments

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!

So the instructions for multi-line comments say the =end needs to be on its own line, and the editor coloring seems to agree. If you have a line starting with =end but with something after it like “=end hello”, then the text color remains the same as a comment until it sees =end by itself on a line.

However, the interpreter seems to think that any line starting with =end is the last line of the comment, and anything directly after =end on the same line remains a comment but lines after that are not.

Here is a screenshot of my tests.

If it’s not in the spec, we should not expect code to run how we want. Ruby has a very well defined and strict interpreter. If the spec says =end gets its own line, then respect that.

This likely traces back to heredoc syntax prescibed in other languages from which Ruby has evolved.

1 Like