Javascript Funky array mishap

function a() {
  var b = ["b"];
  console.log(b);
  //console.log(b.slice());
  b = b.push("bb"); 
}
a();

In a "perfect" world you would think that the console.log would show ["b"] , but wildly enough it shows ["b", "bb"] even though "bb" isn't pushed on until afterwards.

If you do console.log(b.slice()); Then you will get the desired result of ["b"] . Why is that? What's the reason behind this complication? I just want to understand this better so I can better avoid it from happening.

* Note I hit on this same point in a recent question of mine, but this is a much more concise example. @RightSaidFred has led me to this point and has been a huge help so far.

Edit

Runnable example on JSFiddle

---

This is a known problem with console.log .

Instead of turning the parameter into a string when you call the method, the parameter is stored and turned into a string when it's displayed in the UI. As nothing happens in the UI while the function is running, you will see the state of the object as it is when you exit the function.

---

I don't think this is a JavaScript wtf; I think it's a console.log wtf. Based on an answer I saw just yesterday, console.log is likely caching your object. If you replace console.log(b) with alert(b) , you'll see b get displayed, as expected.

Unfortunately convincing console.log to behave in a predictable way is not something I have an answer for.

---

I'm assuming this has to do with the way that console.log() works although you're doing something a little funky when you say:

b = b.push("bb");

you should be able to just say

b.push("bb");

链接地址: http://www.djcxy.com/p/18034.html

上一篇: 将未知数量的参数传递给JS函数

下一篇: JavaScript时髦的数组事故