L2J Server

Since nobody wants to argue on the contribution threads, I'm making this discussion here.
There are lots of people supporting the notion that nested conditionals are bad for readability and thus should be avoided, like, for example, here:
http://www.dreamincode.net/forums/topic ... operators/
http://codereview.stackexchange.com/que ... this-abuse

Example code of a nested conditional: Of course, the problem is lessened if the conditional is broken into multiple lines, like so: but for l2j that would require putting "formatter:off/on" flags around it, which, obviously, nobody is going to do.
Compare that to the following: What is your stance on nested conditionals (taking into consideration real-world examples where variables and values are longer than 1 character) - are they fine or are they bad? Would you avoid them? Why?

Reasonable explanations please, "don't care" does not count.

P.S. I would like to ask mods not to lock this topic just because you don't care about the subject. This is the off-topic section after all.
Also, would be nice if this thread could be turned into a poll.

You are making this cause of 20-30 quests in which is used same nested conditional... and it usually looks almost identical in all of those quests.

None the less i will give a opinion on this, without being stupid.

In those quest, i believe it's totally ok to use it, because it's something that repeats itself in other quests and you memorize it and know what it is.

If this would be used only at 1 place and would not be something that repeats itself and is nested more then 2 times( I believe 2 is still ok because after conditions the results go "true : false : false"). If its more then 2 conditions it does truly become unreadable for any normal human being.

So that puts me kind of in middle of yes and no for nested conditionals.

Thats, my 2 cents

P.S. I cannot turn it into a pool.

I believe there weren't any quests with nested conditionals before you started writing them like that... But if you can prove me wrong, then it's a plus for you.

I don't like long nested conditionals i'd reworked some to few lines as u may have seen in collision getters for example.

Yeah, I noticed. Props for that

They are called nested ternary operators in text books.

Anyway, I'm fine with them if they are not over 3 levels and they won't contain any logic.
Examples of discouraged use would look like: Same as Stackoverflow and other sites, this question is seen as not constructive to me.

It'll depend on the developer(s) writing the code, not much the rest of us can do.

Well i don't like to scroll left-right (Because i have no scroll bar on my mouse )
So as long as they fit on my window its good for meh.

I think the gain in number of lines is clearly not worth the impact on readability.
I'm all for using the ternary conditional operator in simple if-else situations. But nesting them just makes it harder to read, where an if-elseif-else block would immediately be easy to understand.

Well, like I've explained to xban1x privately, my standard for line length in general is "does it fit in 1 line in pastebin/github/my screen?"
To be perfectly honest, I'm one of those who very much like the 80 character line width standard; I've written a lot of code that adheres to that rule and it really looks good and is very readable. For some users that limit is a wee bit higher - 120 characters being another popular width - but the conditionals that have been used in some of the quests committed lately are way longer than that; some even go over 300 characters. That does not even fit in a 1080p screen if the editor is in full-screen mode. As far as I counted on my work PC's screen, 1080p resolution @ normal font size fits about 265 characters when the editor is from one side of the screen to another (Checked in Notepad, which has the narrowest borders). And very few people write code in a layout like that, not with IDEs.

I think it's a matter of developer's preferences. I personally don't use if there are more than 2 of them imbricated. That's the limit where code esthetic doesn't worth the time spent to try to understand the nested condition.

There is really few NEEDED nested conditions on L2 world. If you got some, then you messed somewhere, or probably could recode it better.