YandereDev 02/21/2020 It comes down to two factors. The first factor is readability. if/else statements are extremely easy to understand at a glance. I'll provide an example. Take a look at this: if (Health == 0) { Dead = true; } else { } Dead = false; That reads like an English sentence. "If health is zero, dead is true. If not, dead is false." Even someone who doesn't know anything about code can understand what that text means with a quick glance. Compare that to: switch (Health) { } case 0: Dead = true; default: Dead = false; That doesn't read like an English sentence at all. You have to stop and mentally "decode" it to understand it. This slows you down, and prevents you from working quickly. It halts your productivity and reduces the speed of your development. The second factor is that I often use if/else in situations where it doesn't have any impact on the framerate whatsoever. For example, I might use if/else in a function that only runs on one frame, and never runs again. In that type of function, I might employ a long if/else chain, because it's going to have zero impact on gameplay, but will help make the script much more readable. If I'm working on a function that gets called on every frame, I'm much more likely to use switch statements. I actually use switch statements all over the place in the game's code. The idea that I only use if/else is simply false. There are areas of the game's code where I would prefer to use switch statements, but I actually can't. Switch statements only check one variable, and there are areas in the game's code where a wide variety of different variable types all need to be checked. I actually do plan to refactor the game's code so that this isn't an issue anymore, but not until after Osana is released. (edited)

Share Pin Download More

c sharp c# code discordapp discord

Origin Entry: YandereDev

Notes:

This doesn't even make sense for a use case. There's no reason one should be continuously setting life/death each frame. It SHOULD, however, be the following:

if(health <= 0)
  Die();

File type: png

Resolution: (644px x 1033px)

File size: 126 KB

StreamerBans @StreamerBans Automatizado X Twitch Partner "YandereDev" has been banned! X streamerbans.com/user/yanderede... #twitch #ban #firstban #partner #twitchpartner Twitch Partner "YandereDev" has been banned! Click here to look at their ban history streamerbans.com 2:42 p. m. - 30 oct. 2023 - 866,5 mil Reproducciones Suscribirse Q O

public string GetWeekday Text (DayOfWeek weekday) { } if (weekday == DayOfWeek.Sunday) { Weekday = 0; return "SUNDAY"; } else if (weekday == DayOfWeek. Monday) { Weekday 1; return "MONDAY"; } else if (weekday { = } Weekday = 2; return "TUESDAY"; } else if (weekday == DayOfWeek. Wednesday) { } else if (weekday { == Weekday = 3; return "WEDNESDAY"; } else if (weekday { } else { DayOfWeek. Tuesday) == Weekday = 4; return "THURSDAY"; == Weekday = 5; return "FRIDAY"; DayOfWeek. Thursday) DayOfWeek. Friday) Weekday 6; return "SATURDAY";

View All 75 Images

Moar:

0

YandereDev - Alex Defending if else

PROTIP: Press the ← and → keys to navigate the gallery, 'g' to view the gallery, or 'r' to view a random image.

YandereDev 02/21/2020 It comes down to two factors. The first factor is readability. if/else statements are extremely easy to understand at a glance. I'll provide an example. Take a look at this: if (Health == 0) { Dead = true; } else { } Dead = false; That reads like an English sentence. "If health is zero, dead is true. If not, dead is false." Even someone who doesn't know anything about code can understand what that text means with a quick glance. Compare that to: switch (Health) { } case 0: Dead = true; default: Dead = false; That doesn't read like an English sentence at all. You have to stop and mentally "decode" it to understand it. This slows you down, and prevents you from working quickly. It halts your productivity and reduces the speed of your development. The second factor is that I often use if/else in situations where it doesn't have any impact on the framerate whatsoever. For example, I might use if/else in a function that only runs on one frame, and never runs again. In that type of function, I might employ a long if/else chain, because it's going to have zero impact on gameplay, but will help make the script much more readable. If I'm working on a function that gets called on every frame, I'm much more likely to use switch statements. I actually use switch statements all over the place in the game's code. The idea that I only use if/else is simply false. There are areas of the game's code where I would prefer to use switch statements, but I actually can't. Switch statements only check one variable, and there are areas in the game's code where a wide variety of different variable types all need to be checked. I actually do plan to refactor the game's code so that this isn't an issue anymore, but not until after Osana is released. (edited)

View Gallery Random Image

+ Add a Comment

Comments (0)

There are no comments currently available.

Display Comments

Image Details

1,559 views (13 from today)

Uploaded Sep 17, 2023 at 02:44PM EDT

Origin Entry

Notes

This doesn't even make sense for a use case. There's no reason one should be continuously setting life/death each frame. It SHOULD, however, be the following:

if(health <= 0)
  Die();

click to expand

Tags

Claim Authorship Edit History

About the Uploader

NeatCrown

Entry Moderator

Textile Embed

!https://i.kym-cdn.com/photos/images/newsfeed/002/663/415/874.png!

Today's Top Image Galleries

The Amazing Digital Circus title artwork.

The Amazing Digital Circus

Assassination of UnitedHealthcare CEO Brian Thompson depicting an image of the CEO and the gunman.

Assassination of UnitedHealthcare CEO

Squirrel Girl (Doreen Green)

Squirrel Girl (Doreen Green)

UnitedHealthcare CEO Shooter meme.

Luigi Mangione UHC CEO Shooter