k&r2

[Bill Cunningham]

I copied this code from page 9 k&r 2 and it gives an error that even I
can see. Celsius is uninialized.

/* code */

#include <stdio.h>

main(){
int fahr,celsius,lower,upper,step;
lower=0;
upper=300;
step=20;
fahr=lower;
while (fahr<=upper)
{celsius=5*(fahr-32)/9;
printf("%d\t%d\n",fahr,celsuis;
fahr=farh+step;}}

/*end*/

Celsius is intialized within the body of the while function. Why is this
code from k&r2 not working?

Bill

 

[Walter Roberson]

I copied this code from page 9 k&r 2 and it gives an error that even I
can see. Celsius is uninialized.

/* code */

#include <stdio.h>

main(){
int fahr,celsius,lower,upper,step;
lower=0;
upper=300;
step=20;
fahr=lower;
while (fahr<=upper)
{celsius=5*(fahr-32)/9;
printf("%d\t%d\n",fahr,celsuis;

Did you notice the misspelling of celsius on the above line?

 

[Marco Manfredini]

I copied this code from page 9 k&r 2 and it gives an error that even I
can see. Celsius is uninialized.

/* code */

#include <stdio.h>

main(){
int fahr,celsius,lower,upper,step;
lower=0;
upper=300;
step=20;
fahr=lower;
while (fahr<=upper)
{celsius=5*(fahr-32)/9;
printf("%d\t%d\n",fahr,celsuis;
fahr=farh+step;}}

/*end*/

Celsius is intialized within the body of the while function. Why is this
code from k&r2 not working?

You should read the message again. Isn't it rather "celsuis is
undefined"? celsuis?

And did you get something about "farh"?

 

[Bill Cunningham]

Did you notice the misspelling of celsius on the above line?

No. My mistake then.

 

[CBFalconer]

I copied this code from page 9 k&r 2 and it gives an error that
even I can see. Celsius is uninialized.

/* code */

#include <stdio.h>

main(){
int fahr,celsius,lower,upper,step;
lower=0;
upper=300;
step=20;
fahr=lower;
while (fahr<=upper)
{celsius=5*(fahr-32)/9;
printf("%d\t%d\n",fahr,celsuis;
fahr=farh+step;}}

/*end*/

Celsius is intialized within the body of the while function. Why
is this code from k&r2 not working?

Because that is not the code from K&R.

 

[J. J. Farrell]

I copied this code from page 9 k&r 2 and it gives an error that even I
can see. Celsius is uninialized.

/* code */

#include <stdio.h>

main(){
int fahr,celsius,lower,upper,step;
lower=0;
upper=300;
step=20;
fahr=lower;
while (fahr<=upper)
{celsius=5*(fahr-32)/9;
printf("%d\t%d\n",fahr,celsuis;
fahr=farh+step;}}

/*end*/

Celsius is intialized within the body of the while function. Why is this
code from k&r2 not working?

Most likely because of various typos which make it very different from
the code in K&R2.

 

[Joe Wright]

I copied this code from page 9 k&r 2 and it gives an error that even I
can see. Celsius is uninialized.

/* code */

#include <stdio.h>

main(){
int fahr,celsius,lower,upper,step;
lower=0;
upper=300;
step=20;
fahr=lower;
while (fahr<=upper)
{celsius=5*(fahr-32)/9;
printf("%d\t%d\n",fahr,celsuis;
fahr=farh+step;}}

/*end*/

Celsius is intialized within the body of the while function. Why is this
code from k&r2 not working?

Bill

Mine works..

#include <stdio.h>

int main(void)
{
int fahr, celcius;
int lower, upper, step;

lower = 0;
upper = 300;
step = 20;

fahr = lower;
while (fahr <= upper) {
celcius = 5 * (fahr - 32) / 9;
printf("%d\t%d\n", fahr, celcius);
fahr = fahr + step;
}
return 0;
}

 

[TerryP]

No. My mistake then.

The Typo, the bane of compilation!

I remember I once spent 2 hours trying to find the problem in a program (of
mine) that failed to build, some times I wish they made a compiler that gave
errors like:

file:line !!! PEBKAC !!!
sp,member != sp.member -- you are a blind idiot,

After finally finding out that I had been working to long to notice the
difference between , and . I decided to get a better font xD

 

[Martin Ambuhl]

I copied this code from page 9 k&r 2 and it gives an error that even I
can see. Celsius is uninialized.

It has a value assigned before use, so what's the problem?
[...]
int fahr,celsius,lower,upper,step;
[...]

while (fahr<=upper)
{celsius=5*(fahr-32)/9; [...]
Why is this
code from k&r2 not working?

Is this really the code from K&R2? If it is, perhaps we should retreat
to K&R1, where these lines are
while )fahr <= upper) {
celsius = (5.0/9.0) * (fahr-32.0);

 

[Joachim Schmitz]

Because that is not the code from K&R.

Very helpful answer 8-(
Fortunatly others had been far more helpfull in pointing out the typo(s)

Bye, Jojo

 

[Joachim Schmitz]

I copied this code from page 9 k&r 2 and it gives an error that even
I can see. Celsius is uninialized.

It has a value assigned before use, so what's the problem?
[...]
int fahr,celsius,lower,upper,step;
[...]

while (fahr<=upper)
{celsius=5*(fahr-32)/9; [...]
Why is this code from k&r2 not working?

Is this really the code from K&R2? If it is, perhaps we should retreat to
K&R1, where these lines are
while )fahr <= upper) {
celsius = (5.0/9.0) * (fahr-32.0);

Really? Does K&R1 have such bad typos?

After correction it gives a warning:
implicit conversion from "double" to "int": rounding, sign extension, or
loss of accuracy may result

Bye, Jojo

 

[Joachim Schmitz]

Mine works..

#include <stdio.h>

int main(void)
{
int fahr, celcius;
int lower, upper, step;

lower = 0;
upper = 300;
step = 20;

fahr = lower;
while (fahr <= upper) {
celcius = 5 * (fahr - 32) / 9;
printf("%d\t%d\n", fahr, celcius);
fahr = fahr + step;
}
return 0;
}

Your code might work, but it too misspells celsius.

Bye, Jojo

PS: This is something I notice immediatelly, because Celsius(weg) is the
street I live at... If I have to spell Celsius I usually refer to
Fahrenheit, once with the result that it got spelled "Felsius"

 

[Martin Ambuhl]

I copied this code from page 9 k&r 2 and it gives an error that even
I can see. Celsius is uninialized.

It has a value assigned before use, so what's the problem?
[...]
int fahr,celsius,lower,upper,step;
[...]

while (fahr<=upper)
{celsius=5*(fahr-32)/9; [...]
Why is this code from k&r2 not working?

Is this really the code from K&R2? If it is, perhaps we should retreat to
K&R1, where these lines are
while )fahr <= upper) {
celsius = (5.0/9.0) * (fahr-32.0);

Really? Does K&R1 have such bad typos?

No, that's my typo (and unless I missing something, that is properly
singular).

After correction it gives a warning:
implicit conversion from "double" to "int": rounding, sign extension, or
loss of accuracy may result

While your implementation is free to issue such warnings, they are
hardly required. People with a mania for compiles without warnings
might take this is an indication that they should "fix" the code with a
useless cast. Since casts to "shut the compiler up" are all too
frequently a bad idea, I'm not so sure that the warning is a good idea.

 

[santosh]

I copied this code from page 9 k&r 2 and it gives an error that
even
I can see. Celsius is uninialized.

It has a value assigned before use, so what's the problem?
[...]
int fahr,celsius,lower,upper,step;
[...]

while (fahr<=upper)
{celsius=5*(fahr-32)/9; [...]
Why is this code from k&r2 not working?

Is this really the code from K&R2? If it is, perhaps we should
retreat to K&R1, where these lines are
while )fahr <= upper) {
celsius = (5.0/9.0) * (fahr-32.0);

Really? Does K&R1 have such bad typos?

After correction it gives a warning:
implicit conversion from "double" to "int": rounding, sign extension,
or loss of accuracy may result

I could be wrong but, depending on the value in 'fahr', that statement
might invoke undefined behaviour.

 

[Richard Heathfield]

Joachim Schmitz said:

Your code might work, but it too misspells celsius.

Bye, Jojo

PS: This is something I notice immediatelly,

I note that your spelling flame contains a spelling error. It's
heart-warming to see the old traditions being maintained.

 

[Joachim Schmitz]

Joachim Schmitz said:


I note that your spelling flame contains a spelling error. It's
heart-warming to see the old traditions being maintained.

After all I live at Celsiusweg, not at Immediately Drive

Bye, Jojo

 

[Joachim Schmitz]

While your implementation is free to issue such warnings, they are hardly
required. People with a mania for compiles without warnings might take
this is an indication that they should "fix" the code with a useless cast.
Since casts to "shut the compiler up" are all too frequently a bad idea,
I'm not so sure that the warning is a good idea.

But in this case it tells me that using double arithmetic doesn't buy a
thing in the first place.

Bye, Jojo