Loup

If you have an IF statement and the result is true and you endif, does it automatically go to the end of the loop?

Example:

So if StudentAverage = 92, will it assign Grade = "A", then go to the endo, or will it also assign Grade = "B" becasue 92 is also > 79?

Thanks

__________________
"If you cannot lift the load off another's back, do not walk away. Try to lighten it."
~ Frank Tyger

TheAgent

it will also assign a B...

you need an IF / ELSEIF / ENDIF

or another qualifier on the "B" part... for instance, Average > 79 AND Average < 90...

or... just reverse the order... start with "if Av > 60 then grade = 'D'" and work your way up to "if Av > 89 then grade = 'A'"

you follow?

bingle

Or, if the language supports it, you could use a switch statement.

Mavric98

Or you could use an array, and just do something like:

grade = lettergrades[StudentAverage/10];

__________________
"Hope is for people that don't stand a chance."

SinisterMotives

An "endif" won't automatically break out of the "do while" loop, if that's what you're asking. The outer loop will only be broken if the loop's condition is met or if you use an explicit "break" statement.

Also, intead of individual "if...endif" blocks for each test, you should use an "if...elseif...elseif...else" ladder. A "switch" is generally used to test for equivalence, and not for greater-than and less-than comparisons, although it can be kludged in various ways depending on the language.

vanblah

Depending on the language you can use a SELECT statement too.

TheAgent

SELECT is the same as switch, which is a poor programming construct, and should not be used for great than / less than (equals is ok, but its still a bad idea)...

always use IF / ELSEIF / ELSE and not SELECT or SWITCH whenever you can!

Dilbert1234567

use a select case its easier

select case grade

case 100 to 90
'a
case 80 to 90
'b
case 70 to 80
'c
...

end select

its much esier this way.

__________________
Donate Blood!

"Love is not finding the perfect person, but learning to see an imperfect person perfectly." -Sam Keen

vanblah

I agree that in some situations SELECT is poor programming ... but in a simple application like this one I find that it can be more organized. Such as the way Dilbert1234567 suggested.

DewMan

The simplest thing would be to reverse your logic.

Check for the lowest value first, and the highest value last. Your value will get updated at each intermediate step that the check is valid.

if (score > 60)
grade = d
if(score > 70)
grade = c
if(score > 80)
grade = b
if(score > 90)
grade = a

TheAgent

exactly... that was one of the options i originally gave...

theFez

its simple, but bad programming. if you have a high proportion of good students and/or hit the loop a large number of times you are reassigning your variables 3-4 times per loop. plus forcing the evaluation of the if statement every loop. at least with an if/else loop it drops out of the evaluation once it hits a match.

i think Dilbert1234567's solution is the best.

Mavric98

This is extremely bad programming because you are testing score 4 times no matter what even when at times it would only need to be tested once.

__________________
"Hope is for people that don't stand a chance."

DewMan

True. I didn't say it was efficient. People were giving responses using constructs that weren't used in the pseudocode. I gave him an option that didn't require anything more than what posted already.

-Ever-

I'm new to programming, but I think using an ELSE within the If/End If is the right way to go.

__________________
Embracing the goddess energy within yourselves will bring all of you to a new understanding and valuing of life. A vision that inspires you to live and love on planet Earth. Like a priceless jewel buried in dark layers of soil and stone, Earth radiates her brilliant beauty into the caverns of space and time. Perhaps you are aware of those who watch over your home And experience of this place to visit and play with reality. You are becoming aware of yourself as a gamemaster...
--Acknowledge your weaknesses--

theFez

its a better way to go for sure. the problem with the sequence of
if statements is that each and every if has to be evaluated, then the variable is assigned, and the next if is evaluated. if the evaluation fails, the variable is not set, but even if it succeeds the next if statement is evaluated.

with an if/else with two conditions in the if statement (ie
if(grade <= 100 && grade >= 90){
return 'A';
}
elseif(grade < 90 && grade >= 80){
return 'B';
}


with most compilers and interpreters the if will stop the evaluation on the first fail. It knows that if the first condition fails, an AND is impossible so it kicks out. In a sequence of if/else statements, once one matches, it kicks out of the sequence.

a compiler does a good job of optimizing code if you let it.

__________________
# chmod 111 /bin/Laden