Sure, it is generally in the real-world better to use full if control structures. It comes down preference, the complexity and readability based on a case-by-case.
I just used these as examples to demonstrate the operators, but in the real-world if you are doing quite a few of these repetitive simple structures then it is sometimes better to reach for a ternary operator. It just comes to the circumstance at the time and it is up to the developer to decide whether or not it is worth reaching for it.
I think it would have a great use case if you're building a lot of options in a function or class method.
so instead of this:
$key='default value';if(\array_key_exists('key',$options)){$key=$options['key'];}# But a bunch more ...
But instead we could do a bunch of these:
$key=$options['key']??'default value';
Also, I'd like to say sorry. I don't think we should always be doing the regular if then else statement. As you said, it's case-by-case. Developers should just learn the language instead.
I think everyone should understand how the ternary operators work. Their symbols are similar to that of && or ||.
Must've missed it, because I didn't see any examples of the 'Evlis' operators or null coalescing.
Anyways, thank you for the great article. w^
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey :)
Sure, it is generally in the real-world better to use full if control structures. It comes down preference, the complexity and readability based on a case-by-case.
I just used these as examples to demonstrate the operators, but in the real-world if you are doing quite a few of these repetitive simple structures then it is sometimes better to reach for a ternary operator. It just comes to the circumstance at the time and it is up to the developer to decide whether or not it is worth reaching for it.
But I'm glad you learned something new.
I think it would have a great use case if you're building a lot of options in a function or class method.
so instead of this:
But instead we could do a bunch of these:
Also, I'd like to say sorry. I don't think we should always be doing the regular if then else statement. As you said, it's case-by-case. Developers should just learn the language instead.
I think everyone should understand how the ternary operators work. Their symbols are similar to that of
&&or||.Must've missed it, because I didn't see any examples of the 'Evlis' operators or null coalescing.
Anyways, thank you for the great article. w^