[#796] Re: value of assignment (Re: Order of the value of an expression changed? (PR#579)) — Sean Chittenden <sean@...>
> sean@chittenden.org 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 <sean@chittenden.org> writes:
> > f = Foo.new()
>>>>> "J" == J Herre <jlst@gettysgroup.com> 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 <jlst@gettysgroup.com> writes:
Hi --
On Sat, 8 Feb 2003 06:52:17 +0900
Hi --
On Friday, February 7, 2003, at 03:15 PM, dblack@candle.superlink.net
[#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 -- On Sat, 8 Feb 2003, Ryan Pavlik wrote: > On Sat, 8 Feb 2003 08:15:08 +0900 > > Focusing on this change seems a bit of a red herring to me... if you've > changed SpecializedString#to_i, is it not possible to use your new > semantics? Or is it not possible to provide the old behavior as a > default? You _should_ predict problems a change in #to_i semantics might > cause, because semantic changes usually cause problems. That means that if in 2.0 we go back to having Regexp#match provide String objects in all cases, I have to anticipate that too.... I'm not expecting this kind of flip-flopping, but the point is you *can't* code defensively against all changes in the core language. That's why we have mailing lists to keep informed and discuss changes :-) > > > * Changing a method to do something illogical is possible but > > > questionable. > > > > This is of course true, but very far afield from my question. > > True, but I was addressing the quote "presumably the overridden version > would do something different from the String version". Such a change > is illogical... if to_i no longer converts the string to an int, what > does it do? I don't want to get into the whole design of scanf, which isn't relevant, but in brief, Scanf::FormatSpecifier#to_i(s) is a private method which returns s.to_i unless self matches /^\s*%\*/, in which case it returns nil. (See source for more detail.) Keep in mind that I was expecting this method *not* to be called :-) What I was expecting was String#to_i. David -- David Alan Black home: dblack@candle.superlink.net work: blackdav@shu.edu Web: http://pirate.shu.edu/~blackdav