Hi --

On Sat, 8 Feb 2003 nobu.nokada / softhome.net wrote:

> Hi,
>
> At Sat, 8 Feb 2003 08:15:08 +0900,
> dblack / candle.superlink.net wrote:
> > To bring us back on track: what we're discussing is not whether or how
> > to override methods in subclasses, but the relative merits of the two
> > behaviors of Regexp#match.  Either behavior can be accomodated; I
> > simply want to know the history of why the new one was chosen.
>
> $ ruby-1.6 -e 'class S<String;end; p S.new("abc")[1..2].class'
> S
>
> $ ruby-1.6 -e 'class S<String;end; p S.new("abc")[/a/].class'
> String
>
> Just fixed inconsistency.  It might not be a bug but was an
> unclarified behavior.

This has possible implications for other classes:

  candle:~/hacking/ruby$ irb --simple-prompt
  >> class A < Array; end; A.new.replace([1,2,3]).class
  => A
  >> class A < Array; end; A.new.replace([1,2,3]).map {|x| x}.class
  => Array

(same in 1.6.8 and 1.8.0)


David

-- 
David Alan Black
home: dblack / candle.superlink.net
work: blackdav / shu.edu
Web:  http://pirate.shu.edu/~blackdav