Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Although shadowing should never be used (or just to obfuscate) because it’s confusing, I wanted to completely understand it. And I got this strange thing :
alert(parseInt('123'));//Here, I expected 123 but it's 'overshadowed'
function parseInt(){return 'overshadowed';}
alert(parseInt('123'));//Here it's 'overshadowed' too
Why the first alert output ‘overshadowed’ whereas the function is not modified yet?
P.S : I got inspired by Variable shadowing in JavaScript
In JavaScript, all declarations are implicitly placed at the beginning of the scope (“hoisted”), so it doesn’t matter if the parseInt() definition was at the second, last, or first line.