Why 1 && 2 == 2

Re:Why 1 && 2 == 2 by jes5199 on Thursday July 18, 2013 @11:59PM (#6068255)

ah! I've been trying to write Python lately (I'm more of a Rubyist) and the internet suggested:

truecase if condition else falsecase

which is so inside-out that it hurts.

It didn't occur to me to use the boolean style - I guess I think of that as a perl idiom, and assumed that it would get sneered at in py-land

[ Parent | on HN ]

Re:Why 1 && 2 == 2 by pyre on Friday July 19, 2013 @01:23AM (#6068464)

I've never seen:

  $CONDITION && $TRUE_CASE || $FALSE_CASE

used as a Perl idiom in lieu of:

  $CONDITION ? $TRUE_CASE : $FALSE_CASE

I can't claim to have worked with Perl much prior to Perl 5.6/5.8 though, so it may have been an older idiom (though I doubt it as one of Perl's influences was Awk, which also has a C ternary operator, IIRC).

That said, using truthy/falsey values in Python doesn't seem super common. I surprised a couple of interviewers by doing that while implementing some tree manipulation functions.

[ Parent | on HN ]

Re:Why 1 && 2 == 2 by comex on Friday July 19, 2013 @12:25AM (#6068328)

It was mostly used before the creation of the ternary operator in Python 2.5.

[ Parent | on HN ]