[nergal]

i've never seen ANYTHING in the pawn tutorial about this....

PHP Code:

variable = 1 + (2 < 4 ? 5 : 20); 


Specifically, idk what the "int ? int : int" part means

[arthurdead]

Originally Posted by nergal i've never seen ANYTHING in the pawn tutorial about this.... PHP Code: variable = 1 + (2 < 4 ? 5 : 20);  Specifically, idk what the "int ? int : int" part means

if 2 is less then 4 1 + 5 else 1 + 20 (i might be wrong)

[psychonic]

It's a ternary operator.

https://en.wikipedia.org/wiki/%3F:

[nergal]

Originally Posted by psychonic It's a ternary operator. https://en.wikipedia.org/wiki/%3F:

Thanks for clearing that up Psychonic, but why doesn't the sourcepawn tutorial cover this?

This would've been useful if I had read it from the Conditionals portion of the SourcePawn Intro wiki article.

[berni]

Tenary operators shouldn't be overused because they decrease the readability in favor of code lines.

[Mitchell]

But If statement nests can ruin the look of code also

[Powerlord]

Originally Posted by Mitchell But If statement nests can ruin the look of code also

Sometimes those are a necessary evil.

[Mitchell]

Originally Posted by Powerlord Sometimes those are a necessary evil.

-snip-
i was going to show an example in python, but nvm all i would be doing is changing a one line to 3 lines..

It's better to break up if-statements into methods to handle them, making the code look less bulky in one huge functions.

I just hate having to do:

if(PlayerSettings[client][MClass] == MatMClass_Traitor)
{
	PrintToChat(client, "You are a traitor this round!");
}
else if(PlayerSettings[client][MClass] == MatMClass_Detective)
{
	PrintToChat(client, "You are a detective this round!");
}
else
{
	PrintToChat(client, "You are an innocent this round!");
}

instead of:

PrintToChat(client, "You are a %s this round!", (PlayerSettings[client][MClass] == MatMClass_Traitor) ? "Traitor" : (PlayerSettings[client][MClass] == MatMClass_Detective) ? "Detective" : "Innocent");

[Powerlord]

Originally Posted by Mitchell -snip- i was going to show an example in python, but nvm all i would be doing is changing a one line to 3 lines.. It's better to break up if-statements into methods to handle them, making the code look less bulky in one huge functions. I just hate having to do: if(PlayerSettings[client][MClass] == MatMClass_Traitor) { PrintToChat(client, "You are a traitor this round!"); } else if(PlayerSettings[client][MClass] == MatMClass_Detective) { PrintToChat(client, "You are a detective this round!"); } else { PrintToChat(client, "You are an innocent this round!"); } instead of: PrintToChat(client, "You are a %s this round!", (PlayerSettings[client][MClass] == MatMClass_Traitor) ? "Traitor" : (PlayerSettings[client][MClass] == MatMClass_Detective) ? "Detective" : "Innocent");

...those aren't quite identical due to an for innocent in the first example.

[asherkin]

While, yes, that if..elseif..else list is ugly, there is magical syntax to help for that case:

PHP Code:

switch (PlayerSettings[client][MClass])
{
  case MatMClass_Traitor:
    PrintToChat(client, "You are a traitor this round!");
  case MatMClass_Detective:
    PrintToChat(client, "You are a detective this round!");
  default:
    PrintToChat(client, "You are an innocent this round!");
} 


Which, imo, looks considerably better than both, and still covers the a/an case.