Coding since 11yo, that makes it over 30 years now ~~~
Have a PhD in Comp Sci ~~~
Love to go on bike tours ~~~
I try to stay as generalist as I can in this crazy wide place coding is at now.
That's fine, but for future reference, let's note that a.foo doesn't mean that a is a reference.
It does mean that a and b have the same value, and it does mean that that value is used to find a particular property named 'foo' and modify that.
Which makes me think that all of this 'reference' stuff is something someone made up to try to explain javascript in terms of a language with references, like C++, but which doesn't quite fit.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm signing off the thread btw
That's fine, but for future reference, let's note that a.foo doesn't mean that a is a reference.
It does mean that a and b have the same value, and it does mean that that value is used to find a particular property named 'foo' and modify that.
Which makes me think that all of this 'reference' stuff is something someone made up to try to explain javascript in terms of a language with references, like C++, but which doesn't quite fit.