Excerpts from William Morgan's message of Wed Nov 07 09:35:11 -0800 2007: > Good catch. Fixed in SVN. (Still refusing to use "and" though > :) )
To be clear, idiomatic Ruby is to use and/or for short-cut exit checks like "or return nil", and use && and || for all "normal" boolean comparisons. I'm not just trying to be a jerk! But I did blindly make that change your patch without thinking about what I was doing, so thank you for catching that. -- William <[EMAIL PROTECTED]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
