From: Hidetoshi NAGAI <nagai@...>
Date: 2005-08-03T03:00:16+09:00
Subject: Re: Tk - Ruby/Tk core library design questions

From: email55555@gmail.com
Subject: Re: Tk - Ruby/Tk core library design questions
Date: Wed, 3 Aug 2005 01:21:05 +0900
Message-ID: <1122999376.091739.119310@f14g2000cwb.googlegroups.com>
> Not only the 'wm' command, I also think something like:
> 
> TkScale.new(:form=>10, :to=>100, :value=>40, :variable=>v).pack
> As you can see there is side-effect.
> Hash has no notion of order.
> So the set value 40 will modifiy the variable v
> depend on the order of :value=>40 and :variable=>v

If the order is important, such parameters should not be 
treated on a Hash argument. 
I'll not unify TkScale#value= to the configure hash. 
However, instead of your short example, you can write:
TkScale.new(:from=>10, :to=>100, :variable=>v.set_value(40)).pack
-- 
Hidetoshi NAGAI (nagai@ai.kyutech.ac.jp)