[#11073] segfault printing instruction sequence for iterator — <noreply@...>

Bugs item #10527, was opened at 2007-05-02 14:42

14 messages 2007/05/02
[#11142] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Nobuyoshi Nakada <nobu@...> 2007/05/10

Hi,

[#11188] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Paul Brannan <pbrannan@...> 2007/05/16

On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:

[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>

Hi all.

17 messages 2007/05/25

BUG: next in lambda: 1.8.6 differs from 1.8.4 and 1.9.0

From: David Flanagan <david@...>
Date: 2007-05-30 22:28:59 UTC
List: ruby-core #11367
A toplevel next statement in a lambda does not return a value in 1.8.6, 
but it does in both 1.8.4 and today's 1.9.0 build.

The file lambdanext.rb contains the following code:

def test(p)
   puts "entering method"
   puts p.call()
   puts "exiting method"
end
test(lambda { next "returned from lambda" })

And here is its output for 1.8.4, 1.8.6, and 1.9.0.  Note the "nil" in 
the 1.8.6 run:

$ /usr/bin/ruby -v lambdanext.rb
ruby 1.8.4 (2005-12-24) [i386-linux]
entering method
returned from lambda
exiting method

$ /usr/local/bin/ruby -v lambdanext.rb
ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-linux]
entering method
nil
exiting method

$ /usr/local/bin/ruby1.9 -v lambdanext.rb
ruby 1.9.0 (2007-05-30 patchlevel 0) [i686-linux]
entering method
returned from lambda
exiting method

	David Flanagan

In This Thread

Prev Next