|
|
|
|
|
by EvilTerran
4852 days ago
|
|
there is no place in the article where the author states that a = true and false is prettier than a = true && false Something like this, you mean? I was excited to discover that Ruby has the keywords and and or as boolean operators. I quickly got into the habit of writing all of my boolean statements with these, instead of the more conventional && and ||, because my code became so much readable If you would actually have read the article (or even just the comment you replied to) and paid close attention you would have learned that it said precisely that. |
|