Artbyrobot
!!Cd/+jXhVZy7
10/14/2025, 6:28:47 PM
No.2950839
>>2950554
yes that's same but for hte fact you changed the boolean within the first if which you can't do. Just a rule you have to remember is all
also the if else prevents you from doing this which I do all the time:
f (somePersonIsFat == true && reactingToWeight == true)
{
do something
}
if (somePersonIsFat == false && reactingToWeight == true)
{
do something else
}
and sometimes I have more than just two boolean qualifiers and very often I have more than just two sets as well. So sticking to booleans in this way is more versatile and keeping all code in same format like this is also then more standardized and consistent and thereby easier to get comfortable with and read faster due to familiarity over time with the same setup.
yes that's same but for hte fact you changed the boolean within the first if which you can't do. Just a rule you have to remember is all
also the if else prevents you from doing this which I do all the time:
f (somePersonIsFat == true && reactingToWeight == true)
{
do something
}
if (somePersonIsFat == false && reactingToWeight == true)
{
do something else
}
and sometimes I have more than just two boolean qualifiers and very often I have more than just two sets as well. So sticking to booleans in this way is more versatile and keeping all code in same format like this is also then more standardized and consistent and thereby easier to get comfortable with and read faster due to familiarity over time with the same setup.