Comments on 'Ruby 1.9'

Back

Next

nexus2xl (September 29th, 2008 @ 4:14 am)
"Nothing googley" MUAHAHAHA Proprietary secrets!!
sgharms (September 6th, 2008 @ 1:42 am)
I think Matz is a Buddha. People within a 5 foot radius of him start smiling and feel vaguely smarter and happier.
Shoot3r101 (September 5th, 2008 @ 6:50 pm)
man this guy is SMART holy moly.
scottburton11 (May 7th, 2008 @ 6:59 am)
Emuliator.
natlang1 (May 2nd, 2008 @ 1:21 pm)
Cool, Ruby 2 and Perl 6 will both be released on the same day - Christmas.
kristonholt (April 30th, 2008 @ 10:27 pm)
how do i download ruby? when i try to download it i need a program to open it what should i use?
nkchenz (April 10th, 2008 @ 10:19 am)
very good and interesting
dav231988 (March 12th, 2008 @ 5:07 pm)
Ruby and Matz roxrz!
JonThm (February 28th, 2008 @ 9:39 pm)
GW is nuclear power fiction! Google a stooge.
lfecdr (February 28th, 2008 @ 2:30 pm)
Where I can download subtitles?
s1e (February 27th, 2008 @ 12:21 am)
Hehe, Matz rocks. The last question was a bit awkward, but it showed Ruby's beauty The Hash object at the bottom of the arguments list Matz was explaining about, can actually have the brackets omitted, but is still interpreted as :a => hash. When you want to pass another hash in the parameter, you have to explicitly wrap them both in brackets, or instantiate by Hash#new If you have a function def google(opts) puts opts[:foo] + boo end This is how it looks google {:boo => "foo"}, {:far => "bar"}
s1e (February 27th, 2008 @ 12:20 am)
BUT since the latter hash is actually just for named parameters, you can probably pass both hash and the named param like google {:foo => "bar}, :boo => "far" and Ruby should interpret it fine It's questionable whether Rails should be rewritten to simply use variables instantiated by named params instead of internally deciphering them from an options hash I'm not in posession of 2.0, so I some of this is speculative, hope it helps though :-)

Next