Funny Code

[djr33]

Arie, I'd guess that's because >= is strictly a mathematical operator, so it can't/won't handle non-numerical values properly.



Continuing on the comments discussion, it's always amusing to read a creatively commented script. At the top of my list I think are IPB and SMF forums' code, always complete with very strange sounding comments... something like "//put the dog in the doghouse" or equally strange things.
(Then as I begin to edit things, I begin to make complaints like "//because this is broken!!")

[jscheuer1]

Makes perfect sense.

>=

is a mathematical comparison operator. It type converts the items to be compared to numbers. If one or both of the items being compared is NaN, well NaN is equal to nothing, not even to itself.

When you use == || >, in javascript == is a type non-specific comparison operator, so anything that is roughly equivalent will match.

'1' == 1

is true. In your example it's:

undefined == undefined

As it so happens, I believe that:

null == undefined

and definitely that:

0 == false

those sort of comparisons are also true.

If you want a type specific comparison, use ===

With that undefined === undefined is still true, but those others are not. With type specific comparison you can always first covert both to a chosen type and then see if they're still equal.

I could go on and on with this sort of thing. But I think you get the point.

[molendijk]

Thanks Daniel and John. I get the point.
Arie.

[keyboard]

I have some code that may not be funny, but it surely is funnily strange. It's about how javascript handles and/or statements. An and/or statement is only false when both members of the statement are false (as opposed to either...or statements that are only false when the members are both true or both false).
So this:
Premise: x1=x2
Conclusion: (since x1=x2), 'x1 is bigger than or equal to x2'
is a true statement.

Let's convert that to javascript. If we put:

<script>
var x1, x2;
x1=x2;
if(x1==x2 || x1>x2){alert('CORRECT.\nWe have postulated that x1 is equal to x2, so x1 is equal to or bigger than x2 (inclusive or).')} else {alert('WRONG.\nWe have postulated that x1 is equal to x2, so x1 is equal to or bigger than x2 (inclusive or).\nWhy am I getting this "else" alert that says I`m wrong?')}
</script>

we get the expected result.
But if we put

<script>
var x1, x2;
x1=x2;
if(x1>=x2){alert('CORRECT.\nWe have postulated that x1 is equal to x2, so x1 is equal to or bigger than x2 (inclusive or)')} else {alert('WRONG.\nWe have postulated that x1 is equal to x2, so x1 is equal to or bigger than x2 (inclusive or).\nWhy am I getting this "else" alert that says I`m wrong?')}
</script>

we incorrectly get a non-expected result.
So using '||' gives the expected outcome, whereas '>=' makes trouble.
What makes things even more weird is that '>=' stops annoying us when we assign concrete values to x1 and x2, as in:

<script>
var x1=1, x2=1;
x1=x2;
if(x1>=x2){alert('CORRECT.\nWe have postulated that x1 is equal to x2, so x1 is equal to or bigger than x2 (inclusive or)')} else {alert('WRONG.\nWe have postulated that x1 is equal to x2, so x1 is equal to or bigger than x2 (inclusive or).\nWhy am I getting this "else" alert that says I`m wrong?')}
</script>

What is going on here?
===
Arie.

You lost me at javascript

[molendijk]

Makes perfect sense.

>=

is a mathematical comparison operator. It type converts the items to be compared to numbers. If one or both of the items being compared is NaN, well NaN is equal to nothing, not even to itself.

Yes, I got it. The same holds for

!=

. This explains why

<script>
if(NaN==NaN){alert('CORRECT')} else {alert('WRONG')}
if(NaN!=NaN){alert('CORRECT')} else {alert('WRONG')}
</script>

gives 'WRONG' first, then 'CORRECT'.
Thanks for the enlightment.
Arie.

[bernie1227]

Wow, when did this thread become about actuall code? Just stumbled on some gems:

// I am not sure if we need this, but too scared to delete. 

// I am not responsible of this code.
// They made me write it, against my will.

//Dear future me. Please forgive me. 
//I can't even begin to express how sorry I am. 

options.BatchSize = 300; //Madness? THIS IS SPARTA!

// I have to find a better job

// hack for ie browser (assuming that ie is a browser)

[keyboard]

// this should work. Hold my beer will you?

// 
// Dear maintainer:
// 
// Once you are done trying to 'optimize' this routine,
// and have realized what a terrible mistake that was,
// please increment the following counter as a warning
// to the next guy:
// 
// total_hours_wasted_here = 39
//

// When I wrote this, only God and I understood what I was doing
// Now, God only knows

           
 // MSXML is... special.             
// (Yes, we really do need fifty lines of code for IE and *one* for everything else)

// this code makes the bosses cd tray open at random intervals for no reason. As apparently I dont need to go the bank today.

aComment = 'this is not aComment' # this is aComment

---------------------------------------------------------------------------

Wow, when did this thread become about actuall code?

lol

[bernie1227]

/* Seriously, people will die if you change this */

Thanks for reading my post keyboard, I've already done that one.

[keyboard]

I deny this

[bernie1227]

/* seriously, don't touch this or people will die */

Deny It all you want, doesn't make it false