You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your pseudo-code description of “var a = 2” is exactly what I did think was going on, so that’s clearly working for me. But your description of what’s actually going on doesn’t mention allocating space, so the two descriptions don’t seem to describe the same thing. Where is the memory allocation taking place?
The text was updated successfully, but these errors were encountered:
I have clarified some of the wording around this, as part of the commit that addressed issue #30. Please re-read that section to see if it's any clearer what the distinctions are. Re-open this issue if it needs further work.
However, I don't think this chapter needs to go any deeper than it already is, in terms of getting into how the inner implementation of the engine allocates space in the computer memory's heap, etc. THAT is definitely way too low-level for what happens in JS. Also, it's highly implementation-dependent. One engine could vary wildly from how another engine does it.
So, where we'll arbitrarily choose to draw the line on what details need discussion is to not talk about how memory is allocated. Since JS has no such concept at the language level, and memory allocation/de-allocation are entirely unobservable from code, those feel like unnecessary "weeds" to get lost in.
Your pseudo-code description of “var a = 2” is exactly what I did think was going on, so that’s clearly working for me. But your description of what’s actually going on doesn’t mention allocating space, so the two descriptions don’t seem to describe the same thing. Where is the memory allocation taking place?
The text was updated successfully, but these errors were encountered: