return !(s == 1000); // returning some condition?

[Milhas]

Can i do this?

return !(s == 1000);

I tested it and if it is false it returns 0, but if it is true it returns nothing... Why doesn't it return 1?

[tabstop]

It does return 1. It will return 0 when s is 1000 and 1 otherwise.

[zx-1]

In this instance it would be vastly more readable to say return s != 1000;.

[Milhas]

In this instance it would be vastly more readable to say return s != 1000;.

lol, good point. What was i thinking when i did !( s==1000) ?? xD

[matsp]

a return statment will ALWAYS return something. The code you have above will return either 0 or 1 by definition of the C "boolean" values - even in standard C that doesn't have the "bool" type.

Perhaps you can produce a small compilable example - but I guarantee you that the function returns and will return a value, whatever you do in a return statement [1] - the return value may be RUBBISH, but it will return SOMETHING that is compatible with the return type of the function.

[1] For the pedants - it is of course also possible to write a return-statement that calls a function that never returns - in this case, the return statement doesn't complete, because the called function never returns. This is something other than what Milhas seems to indicate, which is that the function returns but it doesn't give the correct value back.

--
Mats

[Milhas]

It does return 1. It will return 0 when s is 1000 and 1 otherwise.

if i make printf it doesn't, but if i use a IF function that uses that return it works well.
strange, printf bug?

[Milhas]

a return statment will ALWAYS return something. The code you have above will return either 0 or 1 by definition of the C "boolean" values - even in standard C that doesn't have the "bool" type.

Perhaps you can produce a small compilable example - but I guarantee you that the function returns and will return a value, whatever you do in a return statement [1] - the return value may be RUBBISH, but it will return SOMETHING that is compatible with the return type of the function.

[1] For the pedants - it is of course also possible to write a return-statement that calls a function that never returns - in this case, the return statement doesn't complete, because the called function never returns. This is something other than what Milhas seems to indicate, which is that the function returns but it doesn't give the correct value back.

--
Mats

It returns a value that is seen as "true" by any IF condition, but if i use printf to show that return as %i, it only shows when it is 0, it never shows 1.
perhabs null = true?
strange.

[tabstop]

#include <stdio.h>
#include <stdlib.h>

int test(int s) {
	return !(s==1000);
}

int main(void) {
    printf("%i\n", test(999));
	printf("%i\n", test(1000));
}

silverlx:~$ ./temp2
1
0

[matsp]

Please post a small compilable program, and no, it's not returning NULL for true - it will return the integer value 1 (assuming the return type is int).

--
Mats

[Milhas]

Your right, it returns 1.

Thanks for showing it to me