Optimize Code

[tiscavalcanti]

Hello,

 

I have created this code:

 

if (w > maxWidth || h > textHeight) {

if (y < x) {

[y, y]

} else {

[x, x]

}

} else {

[value[0], value[1]]

}

 

It is a piece, but it gives to understand what I want to optimize without the rest.

 

How to modify this code to work with: Switch Statement instead If/Else mode?

 

This is a expression of After Effects.

 

Thanks.

[john_jack]

take a look at this http://www.w3schools.com/js/js_switch.asp

[Ingolme]

The switch statement is not the optimal structure to use in this situation. Why do you want to use it?

[tiscavalcanti]

The switch statement is not the optimal structure to use in this situation. Why do you want to use it?

And something like "switch(true)" work? If not, could edit this code for me, in If/Else same, of a better way?

 

Thanks!

[justsomeguy]

It would, but if you're doing a switch on a boolean it usually makes more sense to use an if/else structure. If your goal is optimization, you don't see big performance increases by using a switch over an if/else structure.

[tiscavalcanti]

It would, but if you're doing a switch on a boolean it usually makes more sense to use an if/else structure. If your goal is optimization, you don't see big performance increases by using a switch over an if/else structure.

I can do this:

 

function getValue() {
switch (true) {
case yB < xA:
return [yB, yB];
default:
return [xA, xA];
}
}


E = getValue();


if (w > maxWidth || h > textHeight){
x = E[0]; y = E[1];
}


[x, y];

Edited December 18, 2015 by tiscavalcanti

[davej]

 

I can do this:

 

Uh, no you can't.

[tiscavalcanti]

 

Uh, no you can't.

Why not?

[davej]

Hmmm... it does work, but what is the point? It reminds me of people who use for( ; ; ){} rather than while(true){}

[justsomeguy]

I can do this:

Yes, you can, but since we're talking about optimizing and efficiency, what does this do for you:

 

switch (true) {
  case yB < xA:
    return [yB, yB];
  default:
    return [xA, xA];
}

that is better than this:

 

if (yB < xA) {
  return [yB, yB];
}
else {
  return [xA, xA];
}

or this:

 

return (yB < xA) ? [yB, yB] : [xA, xA];

[tiscavalcanti]

Really, thanks for all,

justsomeguy

 

davej

 

Ingolme

 

In fact, I wanted to know different ways of dealing with conditions a little more complex. You all helped me realize how many ways I can do the same thing, that's what I needed really. I expressed myself badly.

 

Thanks again!

[tiscavalcanti]

Yes, you can, but since we're talking about optimizing and efficiency, what does this do for you:

 

switch (true) {
  case yB < xA:
    return [yB, yB];
  default:
    return [xA, xA];
}

that is better than this:

 

if (yB < xA) {
  return [yB, yB];
}
else {
  return [xA, xA];
}

or this:

 

return (yB < xA) ? [yB, yB] : [xA, xA];

This way is interesting:

return (yB <xA)? [yB, yB]: [xA, xA];

Could you explain a little more how it works.

The use of interrogation, is something new to me.

[dsonesuk]

Explained here http://www.w3schools.com/js/js_comparisons.asp under 'Conditional (Ternary) Operator'.

[tiscavalcanti]

Explained here http://www.w3schools.com/js/js_comparisons.asp under 'Conditional (Ternary) Operator'.

Thank you too!