Particularily this line:

boolean wasCar = isCar ? true : false;

it's ternary operator. Equivalent to writing

I hate ternary operators. Imo not as readable and I'm sure the compiler doesn't care if it's a ternary operator or if/else.

It has its places, and you'll start to appreciate it as soon as you start working with language that doesn't support them :/ (eg. golang)

eg. it's super useful when using any kind of templating for any reason (rendering website, filling email or document ...)



This post was edited by nuvo on Apr 25 2017 06:52am

hmm ok thanks guys, makes sense
one question though


wouldn't this alone:
boolean wasCar = isCar ? true : false;

^make it so if isCar = true, wasCar = true?
you don't need if (wascar)?

This whole code is pretty useless and you could

and it would do exactly the same, and then wasCar would still be useless as you say.

They are a very good tool to know how to use. There are many places you can use a ternary in place of an if/else and make the code more maintainable, but don't overdo it and nest them.

Ternaries are great when you need an expression instead of a statement, but they're losing relevancy as more programming languages are embracing the "everything is an expression" philosophy. Take Rust, for example:

Almost every language has a conditional expression of some sort.

This post was edited by ASBands on Apr 25 2017 07:16pm

:D

Messy code