Odd Ruby 1.9.1.rc2 error message


#1

Hello,

I’ve been largely successful in compiling Ruby 1.9.1.rc2 and launching
a Rails 2.2.2 with mysql backend but as I pull in the various gems
such as hpricot, thin, mongrel, I’m encountering this “top (required)”
error in many ruby files and not quite sure what it means.

what does this error mean? —> `block in <top (required)>’

My best guess is that it has something to do with either scoping or
inheritance, but I am just not quite sure. If I understood the error
better, I’d know how to make the necessary Ruby syntax changes, but
I’m stumped!

Michael


#2

How come 1.9.1 how come rc2 isn’t on the site announced?

Sent from my iPhone


#3

Hi,

In message “Re: Odd Ruby 1.9.1.rc2 error message”
on Fri, 30 Jan 2009 09:52:31 +0900, mwlang88 removed_email_address@domain.invalid
writes:

|I’ve been largely successful in compiling Ruby 1.9.1.rc2 and launching
|a Rails 2.2.2 with mysql backend but as I pull in the various gems
|such as hpricot, thin, mongrel, I’m encountering this “top (required)”
|error in many ruby files and not quite sure what it means.
|
|what does this error mean? —> `block in <top (required)>’

I think you’ve omitted important part of the message. Could you fully
disclose your error message lines?

          matz.

#4

On Jan 30, 4:48 am, Yukihiro M. removed_email_address@domain.invalid wrote:

|what does this error mean? —> `block in <top (required)>’

I think you’ve omitted important part of the message. Could you fully
disclose your error message lines?

                                                    matz.

Sorry, wasn’t meaning to be cryptic. It was an error I encountered in
several gem packages I was attempting to test out in the 1.9
environment, so I was just seeking a general explanation of what the
error meant.

Installing the Ruby 1.9.1.p0 release that was just announced fixed it
and I’ve since wiped out RC2 (before seeing this request for more
info).

I have yet to see the message again in 1.9.1.p0. If I do encounter,
will definitely update this thread with more info. At any rate, great
work on getting 1.9.1 final released.

Michael