![Don't you hate when you program a machine and it goes crazy doing things your code doesn't allow to happen? [602x433 - 322KB]](https://pic8.co/sh/S7wAD3.png){kind=link}
In the example, it is assumed that you have to store a to reuse the value elsewhere. Something you still see today while it doesn't fit the assignment=condition is while ((c=fgetc(file))!=EOF) in hand-written parsers and the like. You are going to need the value in c in the loop and calling the function again won't work.
In the example, it is assumed that you have to store a to reuse the value elsewhere. Something you still see today while it doesn't fit the assignment=condition is while ((c=fgetc(file))!=EOF) in hand-written parsers and the like. You are going to need the value in c in the loop and calling the function again won't work.
>In the example, it is assumed that you have to store a to reuse the value elsewhere.
a=f(x); if(a) g();
And then you actually can reuse "a" elsewhere
>>In the example, it is assumed that you have to store a to reuse the value elsewhere.
a=f(x);
if(a) g();
And then you actually can reuse "a" elsewhere
that's using two extra characters and a readability whitespace not counting the new line. :p
In c, you can reuse "a" in both cases.
that's using two extra characters and a readability whitespace not counting the new line. :p
In c, you can reuse "a" in both cases.
That's performing an actual conditional check, it's not an affectation instead of a check, within what was supposed to be a check
That's performing an actual conditional check, it's not an affectation instead of a check, within what was supposed to be a check
(post is archived)