Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #14191 > unrolled thread

Difference between == and ===?

Back to article view | Back to comp.lang.javascript

Contents

  Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-28 20:19 -0700
    Re: Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-28 21:46 -0700
      Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-05-29 08:20 +0300
        Re: Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-29 07:56 -0700
          Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-05-29 19:15 +0300
            Re: Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-29 10:35 -0700
              Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-05-29 21:52 +0300
              Re: Difference between == and ===? Gregor Kofler <usenet@gregorkofler.com> - 2012-05-29 21:34 +0200
              Re: Difference between == and ===? Dr J R Stockton <reply1222@merlyn.demon.co.uk.not.invalid> - 2012-05-30 19:53 +0100
                Re: Difference between == and ===? Scott Sauyet <scott.sauyet@gmail.com> - 2012-05-31 04:52 -0700
                  Re: Difference between == and ===? Dr J R Stockton <reply1222@merlyn.demon.co.uk.not.invalid> - 2012-06-01 21:41 +0100
      Re: Difference between == and ===? Gregor Kofler <usenet@gregorkofler.com> - 2012-05-29 09:34 +0200
        Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-05-29 14:13 +0200
          Re: Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-29 08:08 -0700
            Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-05-29 17:32 +0200
              Re: Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-29 08:50 -0700
            Re: Difference between == and ===? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-05-29 16:26 +0000
              Re: Difference between == and ===? Jason Kim <iamjsonkim@gmail.com> - 2012-05-29 10:36 -0700
                Re: Difference between == and ===? Scott Sauyet <scott.sauyet@gmail.com> - 2012-05-29 10:52 -0700
                Re: Difference between == and ===? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-05-29 21:50 +0000
                  Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-05-30 07:46 +0300
                    Re: Difference between == and ===? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-05-30 07:48 +0000
                      Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-05-30 11:08 +0300
                        Re: Difference between == and ===? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-05-30 14:36 +0000
                        Re: Difference between == and ===? John G Harris <john@nospam.demon.co.uk> - 2012-05-30 15:26 +0100
                          Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-05-30 20:17 +0300
                            Re: Difference between == and ===? John G Harris <john@nospam.demon.co.uk> - 2012-06-01 14:54 +0100
                              Re: Difference between == and ===? Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-06-01 13:09 -0700
                                Re: Difference between == and ===? Gene Wirchenko <genew@ocis.net> - 2012-06-01 13:49 -0700
                                  Re: Difference between == and ===? Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-06-01 14:21 -0700
                                Re: Difference between == and ===? John G Harris <john@nospam.demon.co.uk> - 2012-06-03 11:41 +0100
                                  Re: Difference between == and ===? Dr J R Stockton <reply1223@merlyn.demon.co.uk.not.invalid> - 2012-06-04 20:02 +0100
                                    Re: Difference between == and ===? BGB <cr88192@hotmail.com> - 2012-06-05 10:06 -0500
                                      Re: Difference between == and ===? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-06-05 18:12 +0000
                                        Re: Difference between == and ===? BGB <cr88192@hotmail.com> - 2012-06-05 21:23 -0500
                                          Re: Difference between == and ===? Norman Peelman <npeelmandog@cfl.rr.com> - 2012-06-05 23:16 -0400
                                            Re: Difference between == and ===? "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-06-06 07:55 +0300
                                        Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-06 08:27 +0200
                                          Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-06 21:22 +0200
                                        Re: Difference between == and ===? Dr J R Stockton <reply1223@merlyn.demon.co.uk.not.invalid> - 2012-06-06 18:56 +0100
                                          Re: Difference between == and ===? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-06-07 07:12 +0000
                                            Re: Difference between == and ===? Dr J R Stockton <reply1223@merlyn.demon.co.uk.not.invalid> - 2012-06-08 20:11 +0100
                                              Re: Difference between == and ===? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-06-09 14:22 +0000
                                      Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-06 08:28 +0200
                                        Re: Difference between == and ===? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-06-06 09:51 +0000
                                          Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-06 21:22 +0200
                                        Re: Difference between == and ===? BGB <cr88192@hotmail.com> - 2012-06-06 08:35 -0500
                                          Re: Difference between == and ===? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-06-06 21:19 +0200
                    Re: Difference between == and ===? John G Harris <john@nospam.demon.co.uk> - 2012-05-30 15:07 +0100
    Re: Difference between == and ===? John G Harris <john@nospam.demon.co.uk> - 2012-05-30 15:44 +0100
    Re: Difference between == and ===? Stefan Weiss <krewecherl@gmail.com> - 2012-06-01 10:05 +0200
      Re: Difference between == and ===? Ross McKay <au.org.zeta.at.rosko@invalid.invalid> - 2012-06-01 20:05 +1000
      Re: Difference between == and ===? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-06-01 15:56 +0000

Page 1 of 3  [1] 2 3  Next page →

#14191 — Difference between == and ===?

How are they different and how are they used?

[toc] | [next] | [standalone]

#14193

On Monday, 28 May 2012 23:19:04 UTC-4, Jason Kim  wrote:
> How are they different and how are they used?

I just found out that there is no == in javascript. 
There is only ===

[toc] | [prev] | [next] | [standalone]

#14194

2012-05-29 7:46, Jason Kim wrote:

> I just found out that there is no == in javascript.

Consider getting back the money you paid for the book or course where 
you learned that. You have been cheated.

-- 
Yucca, http://www.cs.tut.fi/~jkorpela/

[toc] | [prev] | [next] | [standalone]

#14205

On Tuesday, 29 May 2012 01:20:54 UTC-4, Jukka K. Korpela  wrote:
> 2012-05-29 7:46, Jason Kim wrote:
> 
> > I just found out that there is no == in javascript.
> 
> Consider getting back the money you paid for the book or course where 
> you learned that. You have been cheated.
> 
> -- 
> Yucca, http://www.cs.tut.fi/~jkorpela/

I am reading JavaScript: The Good Parts by Douglas Crockford

In chapter 2, table 2.1, where it talks about operator precedence, under equality, there were only
=== and !==.

Ya, that's why I thought there isn't == in javascript.

[toc] | [prev] | [next] | [standalone]

#14212

2012-05-29 17:56, Jason Kim wrote:

> On Tuesday, 29 May 2012 01:20:54 UTC-4, Jukka K. Korpela  wrote:
>> 2012-05-29 7:46, Jason Kim wrote:
>>
>>> I just found out that there is no == in javascript.
>>
>> Consider getting back the money you paid for the book or course where
>> you learned that. You have been cheated.
>>
>> --
>> Yucca, http://www.cs.tut.fi/~jkorpela/
>
> I am reading JavaScript: The Good Parts by Douglas Crockford

Well, it's a good book, and you won't get your money back, because you 
misread it-

> In chapter 2, table 2.1, where it talks about operator precedence, under equality, there were only
> === and !==.
>
> Ya, that's why I thought there isn't == in javascript.

You were in the "good parts" part, which expresses the author's idea of 
what is good in JavaScript.

The "==" operator is the first topic in Appendix B, the bad parts.

Just remember that it's a biased book. Read it, learn from it, but don't 
believe in it.

-- 
Yucca, http://www.cs.tut.fi/~jkorpela/

[toc] | [prev] | [next] | [standalone]

#14218

On Tuesday, 29 May 2012 12:15:52 UTC-4, Jukka K. Korpela  wrote:
> 2012-05-29 17:56, Jason Kim wrote:
> 
> > On Tuesday, 29 May 2012 01:20:54 UTC-4, Jukka K. Korpela  wrote:
> >> 2012-05-29 7:46, Jason Kim wrote:
> >>
> >>> I just found out that there is no == in javascript.
> >>
> >> Consider getting back the money you paid for the book or course where
> >> you learned that. You have been cheated.
> >>
> >> --
> >> Yucca, http://www.cs.tut.fi/~jkorpela/
> >
> > I am reading JavaScript: The Good Parts by Douglas Crockford
> 
> Well, it's a good book, and you won't get your money back, because you 
> misread it-
> 
> > In chapter 2, table 2.1, where it talks about operator precedence, under equality, there were only
> > === and !==.
> >
> > Ya, that's why I thought there isn't == in javascript.
> 
> You were in the "good parts" part, which expresses the author's idea of 
> what is good in JavaScript.
> 
> The "==" operator is the first topic in Appendix B, the bad parts.
> 
> Just remember that it's a biased book. Read it, learn from it, but don't 
> believe in it.
> 
> -- 
> Yucca, http://www.cs.tut.fi/~jkorpela/

"Read it, learn from it, but don't 
believe in it. "

Thanks for that point.
Which javascript book do you like?

[toc] | [prev] | [next] | [standalone]

#14219

2012-05-29 20:35, Jason Kim wrote:

> Which javascript book do you like?

The other book mentioned in the dusty old FAQ, "JavaScript: The 
Definitive Guide".

-- 
Yucca, http://www.cs.tut.fi/~jkorpela/

[toc] | [prev] | [next] | [standalone]

#14220

Am 2012-05-29 19:35, Jason Kim meinte:

[JavaScript - the Good Parts]

>> Just remember that it's a biased book. Read it, learn from it, but don't
>> believe in it.
>>
>> --
>> Yucca, http://www.cs.tut.fi/~jkorpela/
>
> "Read it, learn from it, but don't
> believe in it. "
>
> Thanks for that point.
> Which javascript book do you like?

(Your quoting is a PITA.)

Anyway, Crockford's book *is* a good book. However, I'd say it is not a 
*suitable* book for absolute beginners.

https://developer.mozilla.org/en/JavaScript/Guide
or
https://developer.mozilla.org/en/A_re-introduction_to_JavaScript

seems to be a good starting point for JS beginners.

Gregor


-- 
http://vxweb.net

[toc] | [prev] | [next] | [standalone]

#14247

In comp.lang.javascript message <19bab390-453f-4efd-b4b9-17de422b2ad7@go
oglegroups.com>, Tue, 29 May 2012 10:35:15, Jason Kim
<iamjsonkim@gmail.com> posted:

>
>Thanks for that point.
>Which javascript book do you like?

You should also download a copy of ECMA 262 5th edition; URL can be
found in the newsgroup FAQ and on my site.

It's not easy reading, and only weird people can read it, first time,
all of the way through at once and enjoy the experience.

But, with its index, and with the search facilities of an adequate PDF
viewer, it's easy enough to search it for specific information with a
reasonable chance of finding what is sought.  One can find section
11.9.1 through the index, or search for the "word" '=='.

The first printing of the book "Pure JavaScript" is amusing for the vast
number of obvious errors that it contains, except in Chapter 9, which is
what I bought it for.  That covers JScript.

-- 
 (c) John Stockton, nr London UK  ?@merlyn.demon.co.uk  IE8 FF8 Op11 Sf5 Cr15
   news:comp.lang.javascript FAQ <http://www.jibbering.com/faq/index.html>.
   <http://www.merlyn.demon.co.uk/js-index.htm> jscr maths, dates, sources.
   <http://www.merlyn.demon.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.

[toc] | [prev] | [next] | [standalone]

#14254

Dr J R Stockton wrote:
> You should also download a copy of ECMA 262 5th edition; URL can be
> found in the newsgroup FAQ and on my site.

And edition 5.1 has recently been officially released in an HTML
format at

    <http://ecma-international.org/ecma-262/5.1/>

  -- Scott

[toc] | [prev] | [next] | [standalone]

#14274

In comp.lang.javascript message <fc8c1d1b-12fc-4b95-ac7f-a02318fc6d2b@h4
1g2000yqm.googlegroups.com>, Thu, 31 May 2012 04:52:28, Scott Sauyet
<scott.sauyet@gmail.com> posted:

>Dr J R Stockton wrote:
>> You should also download a copy of ECMA 262 5th edition; URL can be
>> found in the newsgroup FAQ and on my site.
>
>And edition 5.1 has recently been officially released in an HTML
>format at
>
>    <http://ecma-international.org/ecma-262/5.1/>

That's on my page too, now - half the size - a .mht file.  Thanks.
But two warnings from the W3 validator !!

-- 
 (c) John Stockton, nr London, UK. ?@merlyn.demon.co.uk  Turnpike 6.05  WinXP.
 Web  <http://www.merlyn.demon.co.uk/> - FAQ-type topics, acronyms, and links.
 Command-prompt MiniTrue is useful for viewing/searching/altering files. Free,
 DOS/Win/UNIX now 2.0.6; see <URL:http://www.merlyn.demon.co.uk/pc-links.htm>.

[toc] | [prev] | [next] | [standalone]

#14195

Am 2012-05-29 06:46, schrieb Jason Kim:
> On Monday, 28 May 2012 23:19:04 UTC-4, Jason Kim  wrote:
>> How are they different and how are they used?
>
> I just found out that there is no == in javascript.
> There is only ===

Bullshit. Read about the difference here:

<http://oreilly.com/javascript/excerpts/javascript-good-parts/bad-parts.html>

Gregor


-- 
http://vxweb.net

[toc] | [prev] | [next] | [standalone]

#14199

Gregor Kofler wrote:

> Am 2012-05-29 06:46, schrieb Jason Kim:
>> On Monday, 28 May 2012 23:19:04 UTC-4, Jason Kim  wrote:
>>> How are they different and how are they used?
>>
>> I just found out that there is no == in javascript.

There is no "javascript": <http://PointedEars.de/es-matrix>

>> There is only ===
> 
> Bullshit. Read about the difference here:
> 
> <http://oreilly.com/javascript/excerpts/javascript-good-parts/bad-
parts.html>

Better read there: <http://jibbering.com/faq/#onlineResources>


PointedEars
-- 
Anyone who slaps a 'this page is best viewed with Browser X' label on
a Web page appears to be yearning for the bad old days, before the Web,
when you had very little chance of reading a document written on another
computer, another word processor, or another network. -- Tim Berners-Lee

[toc] | [prev] | [next] | [standalone]

#14206

On Tuesday, 29 May 2012 08:13:10 UTC-4, Thomas 'PointedEars' Lahn  wrote:
> Gregor Kofler wrote:
> 
> > Am 2012-05-29 06:46, schrieb Jason Kim:
> >> On Monday, 28 May 2012 23:19:04 UTC-4, Jason Kim  wrote:
> >>> How are they different and how are they used?
> >>
> >> I just found out that there is no == in javascript.
> 
> There is no "javascript": <http://PointedEars.de/es-matrix>
> 
> >> There is only ===
> > 
> > Bullshit. Read about the difference here:
> > 
> > <http://oreilly.com/javascript/excerpts/javascript-good-parts/bad-
> parts.html>
> 
> Better read there: <http://jibbering.com/faq/#onlineResources>
> 
> 
> PointedEars
> -- 
> Anyone who slaps a 'this page is best viewed with Browser X' label on
> a Web page appears to be yearning for the bad old days, before the Web,
> when you had very little chance of reading a document written on another
> computer, another word processor, or another network. -- Tim Berners-Lee

Thank you, but unlike what the author claims, bringing up ECMAScript probably confuses people even further, since there's the need to explain the history of how javascript came to be and all the browser implement it etc..

Anyways, according to the website, == seems to be deprecated at least in Firefox, while other browsers support it.

[toc] | [prev] | [next] | [standalone]

#14208

Jason Kim wrote:

> Thomas 'PointedEars' Lahn wrote:

Please get a working newsreader.  There was no `'' in my From header 
field value.  And lines in Usenet should no exceed 80 characters; you have 
posted 221 in a single line.

And please do not Cc: me.  I am subscribed to this newsgroup.

>> Gregor Kofler wrote:
>> > Am 2012-05-29 06:46, schrieb Jason Kim:
>> >> On Monday, 28 May 2012 23:19:04 UTC-4, Jason Kim  wrote:
>> >>> How are they different and how are they used?
>> >>
>> >> I just found out that there is no == in javascript.
>> 
>> There is no "javascript": <http://PointedEars.de/es-matrix>
>> 
>> >> There is only ===
>> > 
>> > Bullshit. Read about the difference here:
>> > 
>> > <http://oreilly.com/javascript/excerpts/javascript-good-parts/bad-
>> parts.html>
>> 
>> Better read there: <http://jibbering.com/faq/#onlineResources>
>> 
>> 
>> [signature]

Please learn to quote.  Signatures are not to be quoted unless explicitly 
referred to.  You did not referred to mine, but quoted it regardless.

> Thank you, but unlike what the author claims, bringing up ECMAScript
> probably confuses people even further, since there's the need to explain
> the history of how javascript came to be and all the browser implement it
> etc..

You are mistaken, the record shows.  Which is better, *potentially* 
*temporarily* confused people who are given the possibility to expand on 
their half knowledge, or *all-time* mislead people who don't really know 
what they are doing, causing harm to themselves and others through their 
incompetence?

> Anyways, according to the website, == seems to be deprecated at least in
> Firefox, while other browsers support it.

Utter nonsense, or, as Gregor would probably put it: Bullshit!

The `==' operator is supported since the very beginning (JavaScript 1.0); 
the `===' operator was introduced later.  It is only there are circumstances 
where backwards compatibility does not matter that much that it is less 
error-prone to use the `===' operator.  Learn to read.

Your posting and e-mail are perfect examples of why it is a waste of time to 
read postings injected through Google Groups, which I am therefore usually 
do not do.  Most of the people there do not have the faintest idea what they 
are doing including where they are posting to.


PointedEars
-- 
Sometimes, what you learn is wrong. If those wrong ideas are close to the 
root of the knowledge tree you build on a particular subject, pruning the 
bad branches can sometimes cause the whole tree to collapse.
  -- Mike Duffy in cljs, <news:Xns9FB6521286DB8invalidcom@94.75.214.39>

[toc] | [prev] | [next] | [standalone]

#14210

On Tuesday, 29 May 2012 11:32:49 UTC-4, Thomas 'PointedEars' Lahn  wrote:
> Jason Kim wrote:
> 
> > Thomas 'PointedEars' Lahn wrote:
> 
> Please get a working newsreader.  There was no `'' in my From header 
> field value.  And lines in Usenet should no exceed 80 characters; you have 
> posted 221 in a single line.
> 
> And please do not Cc: me.  I am subscribed to this newsgroup.
> 
> >> Gregor Kofler wrote:
> >> > Am 2012-05-29 06:46, schrieb Jason Kim:
> >> >> On Monday, 28 May 2012 23:19:04 UTC-4, Jason Kim  wrote:
> >> >>> How are they different and how are they used?
> >> >>
> >> >> I just found out that there is no == in javascript.
> >> 
> >> There is no "javascript": <http://PointedEars.de/es-matrix>
> >> 
> >> >> There is only ===
> >> > 
> >> > Bullshit. Read about the difference here:
> >> > 
> >> > <http://oreilly.com/javascript/excerpts/javascript-good-parts/bad-
> >> parts.html>
> >> 
> >> Better read there: <http://jibbering.com/faq/#onlineResources>
> >> 
> >> 
> >> [signature]
> 
> Please learn to quote.  Signatures are not to be quoted unless explicitly 
> referred to.  You did not referred to mine, but quoted it regardless.
> 
> > Thank you, but unlike what the author claims, bringing up ECMAScript
> > probably confuses people even further, since there's the need to explain
> > the history of how javascript came to be and all the browser implement it
> > etc..
> 
> You are mistaken, the record shows.  Which is better, *potentially* 
> *temporarily* confused people who are given the possibility to expand on 
> their half knowledge, or *all-time* mislead people who don't really know 
> what they are doing, causing harm to themselves and others through their 
> incompetence?
> 
> > Anyways, according to the website, == seems to be deprecated at least in
> > Firefox, while other browsers support it.
> 
> Utter nonsense, or, as Gregor would probably put it: Bullshit!
> 
> The `==' operator is supported since the very beginning (JavaScript 1.0); 
> the `===' operator was introduced later.  It is only there are circumstances 
> where backwards compatibility does not matter that much that it is less 
> error-prone to use the `===' operator.  Learn to read.
> 
> Your posting and e-mail are perfect examples of why it is a waste of time to 
> read postings injected through Google Groups, which I am therefore usually 
> do not do.  Most of the people there do not have the faintest idea what they 
> are doing including where they are posting to.
> 
> 
> PointedEars
> -- 
> Sometimes, what you learn is wrong. If those wrong ideas are close to the 
> root of the knowledge tree you build on a particular subject, pruning the 
> bad branches can sometimes cause the whole tree to collapse.
>   -- Mike Duffy in cljs, <news:Xns9FB6521286DB8invalidcom@94.75.214.39>

wow, calm down man. 
Anyways, thanks for the input.

[toc] | [prev] | [next] | [standalone]

#14213

Jason Kim wrote on 29 mei 2012 in comp.lang.javascript:

> Anyways, according to the website, == seems to be deprecated at least
> in Firefox, while other browsers support it. 

What nonsense.
 
Does it seem to be according to that [what?] website,
or does a website say so as you seemingly remember?

Deprecated is not the same as not supported,
deprecated means supported but not forever after anymore.

Javascript is a week-typed language 
so comparison between different types of values is a good thing.

In stromng-typed languages it is not, 
there you have to correct the type before comparison.

Deprecation is not done by Firefox, but by a defining body.

So "deprecated in Firefox" is nonsesnse.

Anyway.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#14214

On Tuesday, 29 May 2012 12:26:27 UTC-4, Evertjan.  wrote:
> Jason Kim wrote on 29 mei 2012 in comp.lang.javascript:
> 
> > Anyways, according to the website, == seems to be deprecated at least
> > in Firefox, while other browsers support it. 
> 
> What nonsense.
>  
> Does it seem to be according to that [what?] website,
> or does a website say so as you seemingly remember?
> 
> Deprecated is not the same as not supported,
> deprecated means supported but not forever after anymore.
> 
> Javascript is a week-typed language 
> so comparison between different types of values is a good thing.
> 
> In stromng-typed languages it is not, 
> there you have to correct the type before comparison.
> 
> Deprecation is not done by Firefox, but by a defining body.
> 
> So "deprecated in Firefox" is nonsesnse.
> 
> Anyway.
> 
> -- 
> Evertjan.
> The Netherlands.
> (Please change the x'es to dots in my emailaddress)

How would you describe the difference between == and ===?

[toc] | [prev] | [next] | [standalone]

#14215

Jason Kim wrote:

> How would you describe the difference between == and ===?

    <https://developer.mozilla.org/en/JavaScript/Reference/Operators/
Comparison_Operators>

  -- Scott

[toc] | [prev] | [next] | [standalone]

#14226

Jason Kim wrote on 29 mei 2012 in comp.lang.javascript:

> How would you describe the difference between == and ===?

I would not, but Google is your friend:

== This is the equal operator and returns a boolean true if both the 
operands are equal. JavaScript will attempt to convert different data types 
to the same type in order to make the comparison.

=== This is the strict equal operator and only returns a boolean true if 
both the operands are equal and of the same type.

<http://www.devguru.com/technologies/ecmascript/quickref/comparison_operato
rs.html>

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | comp.lang.javascript

csiph-web