[#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: value of assignment (Re: Order of the value of an expression changed? (PR#579))
On Monday, February 10, 2003, at 11:33 PM, ts wrote:
> pigeon% cat b.rb
> #!/usr/bin/ruby -Isrc
> require 'bdb'
> bdb = BDB::Btree.open("tmp/aa", nil, "w")
> bdb.set_partial(0, 2)
> if (bdb["blue"] = "XYZ") == bdb["blue"]
> puts "OK #{bdb["blue"]}"
> end
> pigeon%
>
I see your point. I guess maybe you're right. It makes the most sense
if one adopts the policy of having assignment methods return the
result of the assignment. I guess it's not ruby's job to prevent people
from shooting themselves in the foot if they don't want to do that.
FWIW. The case that got me thinking was
((a.b = 42) == a)
which does not seem clear.
Also I think it's easier to explain why
(bdb["blue"] = "XYZ") != bdb["blue"]
under the new behavior, than why
(bdb["blue"] = "XYZ") == bdb["blue"]
doesn't tell you anything about the value of bdb["blue"] under the old.
You'd still need to test that (bdb["blue"] == "XY") to know
that the assignment worked as expected.