(This is a snapshot of my old weblog. New posts and selected republished essays can be found at raganwald.com.)
Monday, November 19, 2007
The best programming tip you'll read today!
Twenty-five plus years of experience. More than three million people using my software. More than fifty million dollars of created value. And it comes down to this:
In Ruby, never type “rescue” when you really meant to type “ensure.”
No need to say it, I know, I know. You’re welcome.
Twenty-five plus years of experience. More than three million people using my software. More than fifty million dollars of created value. And it comes down to this:
In Ruby, never type “rescue” when you really meant to type “ensure.”
No need to say it, I know, I know. You’re welcome.
Comments on “The best programming tip you'll read today!”:
<< Home
Hmm... Not a rubyist, but ensure? That would be a family of higher-order functions that execute a closure given they can prove some precondition is met? As oppose to rescue that tries to recover a failure state?
Quite, this advice is good, and not restricted to Ruby. This advice hit home on a big chunk of the strength of functional programming. This was a nice reminder, and do quite like the name 'ensure'.
Quite, this advice is good, and not restricted to Ruby. This advice hit home on a big chunk of the strength of functional programming. This was a nice reminder, and do quite like the name 'ensure'.
I too thought "ensure" was weird at first... until I couldn't think of something better. It grows on you.
<< Home
