Comments for Ruby, a message to you

Comment on Installing 1.9 by Ruby 1.9 porting notes « Boga Mac blog

Ruby 1.9 porting notes « Boga Mac blog — Sat, 03 May 2008 10:01:16 +0000

[…] Installing ruby 1.9 on MacOSX […]

Comment on Installing 1.9 by Nikos D.

Nikos D. — Mon, 21 Apr 2008 16:06:42 +0000

Migrating to Ruby 1.9 (YARV): Posts you have to re…

So, you are reading everywhere that Ruby 1.9 is faster than 1.8 (even I say so! :D ) and you want to give it a try or even port your existing code to it. Where should you start from?…

Comment on Evil: knowing when a method got passed the default value by Ben Goering

Ben Goering — Wed, 16 Apr 2008 23:00:19 +0000

What a fabulous way to humiliate fools!

Cool post, though. Even a ruby noob like me can understand it!

Comment on Evil: knowing when a method got passed the default value by Chris Shea

Chris Shea — Sun, 13 Apr 2008 15:47:15 +0000

@João: The original problem was that I had a method that should take any object whatsoever and return something based on that, but return something else if the method wasn’t passed anything. A default value of nil wouldn’t help in that case, because the method was expected to handle nil just like everything else.

The solution I ended up with was to rethink my approach. But x=(x_not_given = true) could have worked.

Comment on Evil: knowing when a method got passed the default value by João Paulo Lins

João Paulo Lins — Sun, 13 Apr 2008 15:16:09 +0000

I think to do conditional within method is best, because code is more legible and safe.However is like you said: “Use that at your own peril.”

def greet_world(salutation = nil)
salutation = salutation.nil? ? ‘Hello’ : salutation == ‘Hello’ ? ‘YOU HAVE NO IMAGINATION!’ : salutation
end

Comment on Evil: knowing when a method got passed the default value by crayz

crayz — Sun, 13 Apr 2008 03:57:36 +0000

Wow, just wow. That is ridiculous, but I can actually see it coming in handy sometimes (e.g. maintaining backwards compatibility with an API that’s changing default values in a method call)

Very cool tip

Comment on You might be able to stop trying to call methods on nil by Rails Podcast Brasil - Episódio 8

Rails Podcast Brasil - Episódio 8 — Tue, 01 Apr 2008 14:08:30 +0000

[…] You might be able to stop trying to call methods on nil […]

Comment on Salt Lake City by Corey

Corey — Fri, 28 Mar 2008 18:17:58 +0000

Seriously Chris! You wore the exact same outfit at the last MountainWest RubyConf! http://ruby.tie-rack.org/48/mountainwest-rubyconf/

Comment on Salt Lake City by Peter Jones

Peter Jones — Fri, 28 Mar 2008 15:10:20 +0000

Don’t let Chris fool you, he wears the same outfit every day, not just when he’s in Utah.

Comment on Speeding up gem on OS X Leopard by E. James O'Kelly

E. James O'Kelly — Fri, 28 Mar 2008 00:34:17 +0000

You are my new hero! This has been pissing me off for a long time now and I have had to resource to downloading gems and installing them locally, which obviously keeps me from updating existing gems.

To find where your gem script is just do a:

which gem