StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy are there two kinds of JavaScript strings?
primarykey
Id
5514367
data
AcceptedAnswerId
5514409
AnswerCount
3
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-04-01T13:54:36.210
FavoriteCount
4
LastActivityDate
2011-08-16T01:00:38.003
LastEditDate
2011-04-01T14:00:47.283
LastEditorUserId
251153
OwnerUserId
251153
ParentId
0
PostTypeId
1
Score
35
ViewCount
680
LastEditorDisplayName
text
Body
This one just stabbed me hard. I don't know if it's the case with all browsers (I don't have any other competent browser to test with), but at least Firefox has two kind of string objects. Open up the Firebugs console and try the following: <pre><code>>>> "a" "a" >>> new String("a") String { 0="a"} </code></pre> As you can visually observe, Firefox treats <code>new String("a")</code> and <code>"a"</code> differently. Otherwise however, both kinds of strings seem to behave the same. There is, for instance, evidence that both use the same prototype object: <pre><code>>>> String.prototype.log = function() { console.log("Logged string: " + this); } function() >>> "hello world".log() Logged string: hello world >>> new String("hello world").log() Logged string: hello world </code></pre> So apparently, both are the same. That is, until you ask for the type. <pre><code>>>> typeof("a") "string" >>> typeof(new String("a")) "object" </code></pre> We can also notice that when <code>this</code> is a string, it's always the object form: <pre><code>>>> var identity = function() { return this } >>> identity.call("a") String { 0="a"} >>> identity.call(new String("a")) String { 0="a"} </code></pre> Going a bit further, we can see that the non-object string representation doesn't support any additional properties, but the object string does: <pre><code>>>> var a = "a" >>> var b = new String("b") >>> a.bar = 4 4 >>> b.bar = 4 4 >>> a.bar undefined >>> b.bar 4 </code></pre> Also, fun fact! You can turn a string object into a non-object string by using the <code>toString()</code> function: <pre><code>>>> new String("foo").toString() "foo" </code></pre> Never thought it could be useful to call <code>String.toString()</code>! Anyways. So all these experiments beg the question: why are there two kinds of strings in JavaScript? <hr> Comments show this is also the case for every primitive JavaScript type (numbers and bools included).
Tags
<javascript><string>
Title
Why are there two kinds of JavaScript strings?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USzneak
UserOwnerUserId
1. USzneak
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTDuplicate
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhy are there two kinds of JavaScript strings?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhy are there two kinds of JavaScript strings?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhy are there two kinds of JavaScript strings?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.