₦airaland Forum

GREATIGBOMAN:
The time you used typing this you would have used it to actually test the codes before posting.

Kindly test all what you've written on the console.

When you're done,

This is "L" tag


Add it a necklace and put it on your neck

Bye

I should be telling you that because if I hadn't tested it, I wouldn't have come to tell you you're wrong..

sixpathsofpain:
I should be telling you that because if I hadn't tested it, I wouldn't have come to tell you you're wrong..

OK Sir.
Happy coding

sixpathsofpain:
I should be telling you that because if I hadn't tested it, I wouldn't have come to tell you you're wrong..

You're wrong x = 17

Also I don't think you test the code, they are right, you should study more.

The senior colleagues have spoken.

Imagine the kind of bug we'd be dealing with if you re-asign a value to a variable and the reference catches the change automatically.

It's the reason there is a difference between passing variable by reference and passing it by value. If I'm not capping.

PHP used to do that shiit but they stopped and actually discouraged that since PHP 7 or so.

As a noob, JavaScript runs from top to bottom, the change and reassignment of value you made at the bottom will likely not be effected at the top since the JavaScript machine executes the code from the top to the bottom.

OP quit using VAR, the convention now is to stick with LET and CONST.

As a noob, JavaScript runs from top to bottom, the change and reassignment of value you made at the bottom will likely not be effected at the top since the JavaScript machine executes the code from the top to the bottom.

OP quit using VAR, the convention now is to stick with LET and CONST.

remi1444:
As a noob, JavaScript runs from top to bottom, the change and reassignment of value you made at the bottom will likely not be effected at the top since the JavaScript machine executes the code from the top to the bottom.

OP quit using VAR, the convention now is to stick with LET and CONST.

The exception is an array, when you copy an array, it's copies the reference, just like a pointer in C++,

qtguru:
The exception is an array, when you copy an array, it's copies the reference, just like a pointer in C++,

Oh yesss. Same with Object too. The only way to make a clone excluding future key values will be to use the spread(…) I guess.