Endless loop question

[Tweaxor]

This has been puzzling me all this week. This is actually a homework
assignment
from last semesmter. But the teacher wouldn't tell us why certain
things didn't work, but it didn't just work. My thing was what
actually turn this while loop into an endless loop instead of waiting
for user response it'll would skip right over it. Could someone with
the time explain this to me what would make it behave like this
int pts1, pts2, pts3, wk_exp, p_pay, total_pts, total_pay;
char degree, again;

int main() {
char again = 'Y';

while (again != 'N')
{

printf("\nEnter degree type: (B for Bachelors), (M for Masters), (D
for Doctorate\n");
printf("\t\t\t: ");
scanf("%1c", &degree);
if (degree = 'B') {
pts1 = 3;
}
if (degree = 'M') {
pts1 = 5;
}
if (degree = 'D') {
pts1 =7;
}
printf("\nEnter number of years of work experience: ");
scanf("%2d",&wk _exp);
if (wk_exp <= 3) {
pts2 = 4;
}
if (wk_exp >= 4 && wk_exp <= 6) {
pts2 = 7;
}
if (wk_exp >= 7) {
pts2 = 10;
}

printf("\nEnter current Pay: ");
scanf("%5d",&p_ pay);
if (p_pay <= 15000) {
pts3 = 4;
}
if (p_pay >= 15001 && p_pay <= 22500) {
pts3 = 8;
}
if (p_pay > 22500) {
pts3 = 12;
}

total_pts = pts1 + pts2 + pts3;
if (total_pts <= 19) {
total_pay = 25000;
}
if (total_pts >= 20 && total_pts <= 28) {
total_pay = 30000;
}
else if (total_pts >= 29) {
total_pay = 35000;
}

printf("\nThe pay rate is: %d\n",total_pay );

printf("\nWant to do this again? Press N for NO: ");
/*scanf("%1c", &again); */
getchar();
}

return (0) ;
}

[Mark A. Odell]

ph****@yahoo.co m (Tweaxor) wrote in
news:1c******** *************** ***@posting.goo gle.com:

This has been puzzling me all this week. This is actually a homework
assignment
from last semesmter. But the teacher wouldn't tell us why certain
things didn't work, but it didn't just work. My thing was what
actually turn this while loop into an endless loop instead of waiting
for user response it'll would skip right over it. Could someone with
the time explain this to me what would make it behave like this

None of these seem to need to be defined outside of main().
int pts1, pts2, pts3, wk_exp, p_pay, total_pts, total_pay;
char degree, again;

int main() { Ick ^^^^^^^^

int main(void)
{
char again = 'Y';

while (again != 'N')
{
/*scanf("%1c", &again); */
getchar();
}

return (0) ;

}

Since again is initially == 'Y', explain how again will ever be anything
but 'Y'. Then see why the while loop becomes endless.

--
- Mark ->
--

[S.Tobias]

Mark A. Odell <od*******@hotm ail.com> wrote:

ph****@yahoo.co m (Tweaxor) wrote in
news:1c******** *************** ***@posting.goo gle.com:

int main() {

Ick ^^^^^^^^

int main(void)
{

No, why? You can drop `void' in function definition, can't you?

--
Stan Tobias
sed 's/[A-Z]//g' to email

[Alan Balmer]

On 29 Sep 2004 18:11:07 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

Mark A. Odell <od*******@hotm ail.com> wrote:

ph****@yahoo.co m (Tweaxor) wrote in
news:1c******** *************** ***@posting.goo gle.com:

> int main() {

Ick ^^^^^^^^

int main(void)
{

No, why? You can drop `void' in function definition, can't you?

They mean different things. '(void)' tells the compiler there are no
arguments. '()' tells the compiler that the arguments are unspecified.

--
Al Balmer
Balmer Consulting
re************* ***********@att .net

[Dave Vandervies]

In article <07************ *************** *****@4ax.com>,
Alan Balmer <al******@spamc op.net> wrote:

On 29 Sep 2004 18:11:07 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

Mark A. Odell <od*******@hotm ail.com> wrote:

ph****@yahoo.co m (Tweaxor) wrote in
news:1c******** *************** ***@posting.goo gle.com:

> int main() {
Ick ^^^^^^^^

int main(void)
{

No, why? You can drop `void' in function definition, can't you?

They mean different things. '(void)' tells the compiler there are no
arguments. '()' tells the compiler that the arguments are unspecified.

In this case, though, the distinction doesn't make any difference; one
form means "Here's the definition of a function called main, returning
int and taking no arguments, without a prototype" and the other form
means "Here's the definition of a function called main, returning int
and taking no arguments, with a prototype".

Unless, of course, you're planning on calling main later on with a
nonempty argument list. But if you really want to lie to the compiler,
a prototype won't stop you either.
dave
((int (*)())main)(arg v,argc);

--
Dave Vandervies dj******@csclub .uwaterloo.ca
Shoot. Maybe I should port [GCC] to MMIX to get some [experience]
on my own.
--Ben Pfaff in comp.lang.c

[S.Tobias]

Alan Balmer <al******@att.n et> wrote:

On 29 Sep 2004 18:11:07 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

No, why? You can drop `void' in function definition, can't you?

They mean different things. '(void)' tells the compiler there are no
arguments. '()' tells the compiler that the arguments are unspecified.

In declarations that are not definitions.

What can be unspecified in function definition?
int f() {}

Grep through n869.txt - there are two examples using "int main()"
(and one "int main(void)") declaration. They wouldn't miss an error
like that, would they?

--
Stan Tobias
sed 's/[A-Z]//g' to email

[187]

Alan Balmer wrote:

On 29 Sep 2004 18:11:07 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

Mark A. Odell <od*******@hotm ail.com> wrote:

ph****@yahoo.co m (Tweaxor) wrote in
news:1c******** *************** ***@posting.goo gle.com:

int main() {
Ick ^^^^^^^^

int main(void)
{

No, why? You can drop `void' in function definition, can't you?

They mean different things. '(void)' tells the compiler there are no
arguments. '()' tells the compiler that the arguments are unspecified.

but when it coems down to it, I've never seen any difference in actual
behavior between the two. When it comes to normal functions, there is no
difference.

[Flash Gordon]

On Wed, 29 Sep 2004 18:30:11 +0000 (UTC)
dj******@csclub .uwaterloo.ca (Dave Vandervies) wrote:

In article <07************ *************** *****@4ax.com>,
Alan Balmer <al******@spamc op.net> wrote:

On 29 Sep 2004 18:11:07 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

Mark A. Odell <od*******@hotm ail.com> wrote:
ph****@yahoo.co m (Tweaxor) wrote in
news:1c******** *************** ***@posting.goo gle.com:

> int main() {
Ick ^^^^^^^^

int main(void)
{

No, why? You can drop `void' in function definition, can't you?
They mean different things. '(void)' tells the compiler there are no
arguments. '()' tells the compiler that the arguments are
unspecified.

In this case, though, the distinction doesn't make any difference; one
form means "Here's the definition of a function called main, returning
int and taking no arguments, without a prototype" and the other form
means "Here's the definition of a function called main, returning int
and taking no arguments, with a prototype".

So why not give the compiler all the information you have? It's
generally a good habit and if you[1] break it for main you are likely to
break it for other functions.
Unless, of course, you're planning on calling main later on with a
nonempty argument list. But if you really want to lie to the
compiler, a prototype won't stop you either.

Actually, if there is a prototype in scope and you pass an incorrect
number of parameters the compiler is (I believe) *required* to produce a
diagnostic.

[1] The generic you, not the specific you.
--
Flash Gordon
Sometimes I think shooting would be far too good for some people.
Although my email address says spam, it is real and I read it.

[Mark A. Odell]

"S.Tobias" <sN*******@amu. edu.pl> wrote in
news:2s******** *****@uni-berlin.de:

> int main() {

Ick ^^^^^^^^

int main(void)
{

No, why? You can drop `void' in function definition, can't you?

I just said "Ick", it's not wrong, just lazy IMHO.

--
- Mark ->
--

[Alan Balmer]

On 29 Sep 2004 19:00:34 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

Alan Balmer <al******@att.n et> wrote:

On 29 Sep 2004 18:11:07 GMT, "S.Tobias" <sN*******@amu. edu.pl> wrote:

>No, why? You can drop `void' in function definition, can't you?

They mean different things. '(void)' tells the compiler there are no
arguments. '()' tells the compiler that the arguments are unspecified.

In declarations that are not definitions.

What can be unspecified in function definition?
int f() {}

Grep through n869.txt - there are two examples using "int main()"
(and one "int main(void)") declaration. They wouldn't miss an error
like that, would they?

The examples are not the standard. Your copy of the draft probably
includes section 5.1.2.2.1, paragraph 1, which gives the two allowable
forms, plus allows other *implementation-defined* forms. If the OP's
implementation documents that usage, it's OK. It probably doesn't.

--
Al Balmer
Balmer Consulting
re************* ***********@att .net