[#796] Re: value of assignment (Re: Order of the value of an expression changed? (PR#579)) — Sean Chittenden <sean@...>
> [email protected] wrote:
Hi,
> |I have read the thread and I think this is a pretty bad change. I
Hi,
> > #BEGIN test.rb
Hi,
Hi --
Hi,
Hi --
Hi,
Hi,
Hi,
what about if attr_accessor :foo defined three methods - #foo, #foo=, and
> |What was wrong with having the receiver set the return value though?
Sean Chittenden <[email protected]> writes:
> > f = Foo.new()
>>>>> "J" == J Herre <[email protected]> writes:
On 11 Feb 2003 at 11:13, Sean Chittenden wrote:
[#801] class of $1, $2 in 1.8.0 — dblack@...
Hi --
Hi,
Hi --
Hi,
Hi --
J.Herre <[email protected]> writes:
Hi --
On Sat, 8 Feb 2003 06:52:17 +0900
Hi --
On Friday, February 7, 2003, at 03:15 PM, [email protected]
[#851] Alternate GC ? — Mathieu Bouchard <matju@...>
[#875] OpenSSL for Ruby 0.2.0-pre0 — Michal Rokos <michal@...>
Hi everybody!
[#889] Bob Jenkins' hashing implementation in Ruby — Mauricio Fern疣dez <batsman.geo@...>
>>>>> "M" == Mauricio Fern疣dez <Mauricio> writes:
On Sat, Mar 01, 2003 at 08:42:40PM +0900, ts wrote:
>>>>> "M" == Mauricio Fern疣dez <Mauricio> writes:
On Sat, Mar 01, 2003 at 10:03:47PM +0900, ts wrote:
>>>>> "M" == Mauricio Fern疣dez <Mauricio> writes:
On Sat, Mar 01, 2003 at 10:10:35PM +0900, ts wrote:
Hi,
[#890] String and (repost) MemLeak — Michal Rokos <michal@...>
Hi,
Hi,
Hi,
Hi,
Hi,
Re: class of $1, $2 in 1.8.0
Hi -- (Replying to two posts here.) On Sat, 8 Feb 2003, Matt Armstrong wrote: > J.Herre <[email protected]> writes: > > > On Friday, February 7, 2003, at 08:05 AM, [email protected] > > wrote: > > > >> class SpecializedString < String > >> def to_i(s) > >> # specialized overriding of to_i > >> end > >> end > >> > >> s = SpecializedString.new("12345") > >> m = /(\d\d)/.match(s) > >> n = m[1].to_i > >> p n * 10 > > > > This regexp change is actually very cool. I've got some ugly code > > that I can fix up as a result of this change. > > > > FWIW I think your example argues more strongly for adding > > multi-dispatch to ruby (or maybe just adopting a policy of not Yikes -- I assure you that's unintentional :-) > > changing the semantics of well-known methods in subclasses) than for > > backing out this change. There's no way to define "well-known" robustly in that context, though. Also, even if the semantics weren't changed (I assume you mean the argument count), presumably the overridden version would do something different from the String version, so this 1.8.0 shift would still have an impact. I can always do: n = String.new(m[1]).to_i but I'm not fond of it. > At the risk of a "me too" post, I have the same thoughts. Code should > be able to do tests for object.kind_of?(String) and expect the methods > of String to be present with similar semantics. We're well into "agree to disagree" territory here :-) I tend to look at the behavior of Ruby objects as being very in-the-moment. But in any case, mainly I'm just wondering what the impetus was for this particular change to #match (and #scan and #split). David -- David Alan Black home: [email protected] work: [email protected] Web: http://pirate.shu.edu/~blackdav