Too bad, for me it is. I dont like to take other people concepts or ideas but When i came to this idea it was Crystal clear to me. I'll try to find good arguments in favor ^^

Gauthier Wallet
Envoyé depuis mon iPhone.

Le 11 févr. 2013 à 22:18, Charles-Emmanuel <notifications@github.com> a écrit :

> In bash/log.inc.sh:
> 
> > +}
> > +
> > +# Write a light box on console. Available color : blue
> > +function printLightBox() {
> > +
> > +    LIGHTBOX_COLOR="$1"
> > +    LIGHTBOX_TEXT="$2"
> > +    LIGHTBOX_SPACE=" "
> > +
> > +    # One lightbox line must contain 80 letters.
> > +    while [ ${#LIGHTBOX_TEXT} -lt 80 ]
> > +    do
> > +        LIGHTBOX_TEXT="${LIGHTBOX_TEXT}${LIGHTBOX_SPACE}"
> > +    done
> > +
> > +    if [ ${LIGHTBOX_COLOR} == "blue" ]; then
> I really don't understand "Yoda conditions". Today was not a good day for me, so I took the time to think about this.
> A good code must be readable, we should not be forced to assemble code in the good order to decrypt it.
> 
> In my opinion, a condition can be translated to "If my variable is equal to this value, do..."
> In your case, you say : "If blue is the sky" instead of "If the sky is blue, do...".
> 
> I've read more about this on Internet. At the beginning, it was used in Java to avoid "null pointer exception" in "if" conditions, or accidental assignments in others languages. But this question separates developers, and stack overflow has been forced to delete an animated conversation (http://stackoverflow.com/questions/2349378/new-programming-jargon-you-coined).
> (Or you can read this about the stack overflow topics : http://www.codinghorror.com/blog/2012/07/new-programming-jargon.html)
> 
> So, so, so... I don't take a decision this evening about this, but, definitely, I don't think it's really rational.
> 
> —
> Reply to this email directly or view it on GitHub.
>