From: Ola Bini <ola.bini@...>
Date: 2008-04-19T00:08:38+09:00
Subject: Strange changes in Enumerator

Hi,

While looking through the differences in 1.8.7 and trying to find the 
matching changes in the ChangeLog it seems that some things have 
happened that breaks backwards compatibility while not being documented. 
Specifically, JRuby's testEnumerator suite have some failures because 
when enumerator was backported from 1.9, some changes in that break 
existing functionality.

Specific examples:
Enumerator#each_slice and Enumerator#enum_slice is now the same method, 
while enum_slice used to have different semantics with regards to 
arguments and error reporting.
The same thing seems to have happened with Enumerator#each_cons and 
Enumerator#enum_cons.

Also, something like
  Enumerable::Enumerator.new(Object.new).each {}
will now raise a NameError instead of a NoMethodError

Are these conscious changes, and why can't I find any mention of them in 
that case?

Cheers

-- 
 Ola Bini (http://ola-bini.blogspot.com) 
 JRuby Core Developer
 Developer, ThoughtWorks Studios (http://studios.thoughtworks.com)
 Practical JRuby on Rails (http://apress.com/book/view/9781590598818)

 "Yields falsehood when quined" yields falsehood when quined.