OK. First off, I want to apologize for my irresponsible response. It
wasn't fair of me to be so harsh for being told to go read more. I was
tired, and should have left the keyboard alone, but that isn't your
problem, it's mine.
Next, my original question sparked a secondary question while I was
figuring out the solution on my own. The secondary question being the
ERB vs Ruby question
That question was one of 'principle' and 'theory', not of practicality.
I was trying to understand the 'why', not the 'I broke this, help me fix
it' type of question.
David summed it up well, that 'each' returns it's reciever, and his book
(which I just got ahold of this morning for reference), summed up the
same thing. And the output of the reciever in a ruby script prints
nothing, while the output of ERB is to spit out the text of the
I agree that there is a lot of documentation out there to read, but for
me, there is still a lot that is uncorrellated (like each/erb) that I
think is fair game to ask as a question.
The original responder said that I needed to read more and not ask
questions that are readily available. I don't believe that the answer to
this question was 'readily available'
David, you called me on the carpet and you are right. The books do
cover ERB, however, as I read them, they didn't seem to answer my
question, because they didn't cover or warn about printing the return
value of something like each.
Again, I apologize for running astray with my response, and I hope you
can forgive me for such a stretch of temp insanity.
And thank you everyone for being genuinely concerned enough to respond,
and clear this up.