From: "Hal E. Fulton" <hal9000@...>
Date: 2001-11-03T17:37:57+09:00
Subject: [ruby-talk:24254] Re: "yield called out of block"

----- Original Message -----
From: Brian F. Feldman <green@FreeBSD.org>
To: ruby-talk ML <ruby-talk@ruby-lang.org>
Sent: Friday, November 02, 2001 9:24 PM
Subject: [ruby-talk:24246] Re: "yield called out of block"


> matz@ruby-lang.org (Yukihiro Matsumoto) wrote:
> > Hi,
> >
> > In message "[ruby-talk:24183] "yield called out of block""
> >     on 01/11/03, Mark Slagell <ms@iastate.edu> writes:
> >
> > |How about any of the following:
> > |
> > |  "yield called but no block given"
> > |  "there is nothing to yield to"
> > |  "an iterator usually needs to be given something to do" ;-)
> > |
> > |Anyway, the current message doesn't quite seem to capture what is
wrong.
> > |My correpondent was convinced there was something wrong with the
> > |iterator method.
> >
> > "no block to yield"?
>
> It would sound fine if you just were to change the "out" in the original
> exception to "outside".

I think I would say "No block specified with iterator call."
Is that misleading in any way?

Hal