From: david@...
Date: 2006-12-21T20:32:46+09:00
Subject: Re: Assignment method strangeness

Cit�t Ryan Williams <mr.cruft@gmail.com>:
> test.a = { some_other_object.b }
> some_other_object.b = 42
> test.a = 42
> 

1. The sheer memory leak of it all. Ruby apparently isn't made to be a good
functional language, even if it's very doable. Also, it looks like a design
smell to me - why can't you use some_other_object.b in the first place, or move
the data into test.a or somewhere else altogether? To me it seems you'd use that
when you can't decide where some data / state actually belongs.

2. Any code where:

foo.bar = baz
foo.bar == baz # => false

makes me want to scream. YMMV. Assignment being a syntactic builtin to the
language with a certain behaviour is a notion too burned into my brain for
juggling the possibility that it isn't to be an option.

David Vallner