what do these signs mean?

[Mshine67]

Don't even bother yourself with it, unless you plan on doing coding in the future.

[[MPGH]Psychotic]

I think it's != , not =!.

Yeah this.

[Paul]

Yeah this.

No, not this

[radnomguywfq3]

DEAR MOTHER OF FUCKING GOD GUYS.

!= is the valid expression. != is not equal to.

a=!b is the assignment operator then the negation operator. If you seperate the tokens, it becomes a lot cleaer (a = !b).
So

if(y=!false) {}
will always execute, no matter what y is equal to. You assign 'y' to !x, !(false), is evauluted as true.

if( (y=!false) ) {} is if(y = true){}, which, as an expression is always true.

Sure y=!false compiles, but it doesn't do anything like what you think it does. Seriously, slap yourselfs in the face for having this large of a discussion over this nonsense.

---------- Post added at 01:47 AM ---------- Previous post was at 01:36 AM ----------

Both are the same for everything that it applies to I believe.

No :S Your tests weren't done properly. In the second bit, you assign y to !NULL, or !(0) or !false, which is true.

Test=!NULL is
Test=!(0) is
Test=!false is
Test=true

is if(Test = true) {this will always execute, because you are evauluating the expression (Test = true), which is evaluated as an expression as true.

(y in my debugger is initally true (it wasn't initilized by the first picture), but after the assignment operation at the breakpoint, it was assigned to false.)


Read my explanation above.

[[MPGH]Psychotic]

DEAR MOTHER OF FUCKING GOD GUYS.

!= is the valid expression. != is not equal to.

a=!b is the assignment operator then the negation operator. If you seperate the tokens, it becomes a lot cleaer (a = !b).
So

if(y=!false) {}
will always execute, no matter what y is equal to. You assign 'y' to !x, !(false), is evauluted as true.

if( (y=!false) ) {} is if(y = true){}, which, as an expression is always true.

Sure y=!false compiles, but it doesn't do anything like what you think it does. Seriously, slap yourselfs in the face for having this large of a discussion over this nonsense.

---------- Post added at 01:47 AM ---------- Previous post was at 01:36 AM ----------


No :S Your tests weren't done properly. In the second bit, you assign y to !NULL, or !(0) or !false, which is true.

Test=!NULL is
Test=!(0) is
Test=!false is
Test=true

is if(Test = true) {this will always execute, because you are evauluating the expression (Test = true), which is evaluated as an expression as true.

(y in my debugger is initally true (it wasn't initilized by the first picture), but after the assignment operation at the breakpoint, it was assigned to false.)


Read my explanation above.

Don't know why you went through all that just to explain to people that it's the right expression.

[[MPGH]Flengo]

DEAR MOTHER OF FUCKING GOD GUYS.

!= is the valid expression. != is not equal to.

a=!b is the assignment operator then the negation operator. If you seperate the tokens, it becomes a lot cleaer (a = !b).
So

if(y=!false) {}
will always execute, no matter what y is equal to. You assign 'y' to !x, !(false), is evauluted as true.

if( (y=!false) ) {} is if(y = true){}, which, as an expression is always true.

Sure y=!false compiles, but it doesn't do anything like what you think it does. Seriously, slap yourselfs in the face for having this large of a discussion over this nonsense.

---------- Post added at 01:47 AM ---------- Previous post was at 01:36 AM ----------


No :S Your tests weren't done properly. In the second bit, you assign y to !NULL, or !(0) or !false, which is true.

Test=!NULL is
Test=!(0) is
Test=!false is
Test=true

is if(Test = true) {this will always execute, because you are evauluating the expression (Test = true), which is evaluated as an expression as true.

(y in my debugger is initally true (it wasn't initilized by the first picture), but after the assignment operation at the breakpoint, it was assigned to false.)


Read my explanation above.

Thanks for the explanation, you're right

[3amour]

It means not equal.