JavaScript Hoisting: Function Can Refer to Another Function Declared Below It?How can I merge properties of two JavaScript objects dynamically?How can I convert a string to boolean in JavaScript?What's the difference between using “let” and “var”?Set a default parameter value for a JavaScript functionHow can I get query string values in JavaScript?How do I include a JavaScript file in another JavaScript file?How can I pretty-print JSON using JavaScript?Is there a standard function to check for null, undefined, or blank variables in JavaScript?Javascript function scoping and hoistingJavaScript 'hoisting'

Maximum likelihood parameters deviate from posterior distributions

Java Casting: Java 11 throws LambdaConversionException while 1.8 does not

How to determine what difficulty is right for the game?

Do infinite dimensional systems make sense?

Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)

Arrow those variables!

How can bays and straits be determined in a procedurally generated map?

Cross compiling for RPi - error while loading shared libraries

How is it possible to have an ability score that is less than 3?

infared filters v nd

How much of data wrangling is a data scientist's job?

What's the output of a record needle playing an out-of-speed record

Today is the Center

meaning of に in 本当に?

Why is 150k or 200k jobs considered good when there's 300k+ births a month?

Is it tax fraud for an individual to declare non-taxable revenue as taxable income? (US tax laws)

Why does Kotter return in Welcome Back Kotter?

How does quantile regression compare to logistic regression with the variable split at the quantile?

Languages that we cannot (dis)prove to be Context-Free

What does "Puller Prush Person" mean?

Malformed Address '10.10.21.08/24', must be X.X.X.X/NN or

Are the number of citations and number of published articles the most important criteria for a tenure promotion?

Replacing matching entries in one column of a file by another column from a different file

Is it inappropriate for a student to attend their mentor's dissertation defense?



JavaScript Hoisting: Function Can Refer to Another Function Declared Below It?


How can I merge properties of two JavaScript objects dynamically?How can I convert a string to boolean in JavaScript?What's the difference between using “let” and “var”?Set a default parameter value for a JavaScript functionHow can I get query string values in JavaScript?How do I include a JavaScript file in another JavaScript file?How can I pretty-print JSON using JavaScript?Is there a standard function to check for null, undefined, or blank variables in JavaScript?Javascript function scoping and hoistingJavaScript 'hoisting'






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I have:



// Shouldn't we have the following hoisted?
// var multiply; (undefined)
// var add; (undefined)

var multiply = function(num)
return add(num) * 2;
;

var add = function(num)
return num + 1;
;

console.log(multiply(1)); // No error, somehow "multiply" calls "add"!


I thought that JavaScript variables are hoisted to the top, but not the values that they are assigned to. Somehow multiply calling add doesn't return an error, even though add is declared below multiply.










share|improve this question
























  • I think so, based on my admittedly flawed memory of reading this blog.bitsrc.io/…, which might teach you more than you wanted to know. The basics I remember include that each function gets its own execution context which includes a couple of internal lexical environments (one of which is specific to those identifiers declared with var) and these lexical environments can access the outer environment. Also, I think var and function declarations get hoisted but let and const declarations don't...

    – Cat
    Mar 9 at 1:32











  • The explanation is pretty simple. JS lets your functions reference variables that don't exist. So the potential for error only comes after the function is invoked. At the time of invocation, if the referenced variable doesn't exist, you get an error. As a test, remove the add() function, and update multiply() so that it uses a try/catch, where the try tries to call add(), and the catch creates it at window.add = function() .... You'll see that the ReferenceError is caught on the first invocation, but subsequent invocations succeed.

    – ziggy wiggy
    Mar 9 at 1:50












  • ...like this: jsfiddle.net/cpzj309w

    – ziggy wiggy
    Mar 9 at 1:53

















1















I have:



// Shouldn't we have the following hoisted?
// var multiply; (undefined)
// var add; (undefined)

var multiply = function(num)
return add(num) * 2;
;

var add = function(num)
return num + 1;
;

console.log(multiply(1)); // No error, somehow "multiply" calls "add"!


I thought that JavaScript variables are hoisted to the top, but not the values that they are assigned to. Somehow multiply calling add doesn't return an error, even though add is declared below multiply.










share|improve this question
























  • I think so, based on my admittedly flawed memory of reading this blog.bitsrc.io/…, which might teach you more than you wanted to know. The basics I remember include that each function gets its own execution context which includes a couple of internal lexical environments (one of which is specific to those identifiers declared with var) and these lexical environments can access the outer environment. Also, I think var and function declarations get hoisted but let and const declarations don't...

    – Cat
    Mar 9 at 1:32











  • The explanation is pretty simple. JS lets your functions reference variables that don't exist. So the potential for error only comes after the function is invoked. At the time of invocation, if the referenced variable doesn't exist, you get an error. As a test, remove the add() function, and update multiply() so that it uses a try/catch, where the try tries to call add(), and the catch creates it at window.add = function() .... You'll see that the ReferenceError is caught on the first invocation, but subsequent invocations succeed.

    – ziggy wiggy
    Mar 9 at 1:50












  • ...like this: jsfiddle.net/cpzj309w

    – ziggy wiggy
    Mar 9 at 1:53













1












1








1








I have:



// Shouldn't we have the following hoisted?
// var multiply; (undefined)
// var add; (undefined)

var multiply = function(num)
return add(num) * 2;
;

var add = function(num)
return num + 1;
;

console.log(multiply(1)); // No error, somehow "multiply" calls "add"!


I thought that JavaScript variables are hoisted to the top, but not the values that they are assigned to. Somehow multiply calling add doesn't return an error, even though add is declared below multiply.










share|improve this question
















I have:



// Shouldn't we have the following hoisted?
// var multiply; (undefined)
// var add; (undefined)

var multiply = function(num)
return add(num) * 2;
;

var add = function(num)
return num + 1;
;

console.log(multiply(1)); // No error, somehow "multiply" calls "add"!


I thought that JavaScript variables are hoisted to the top, but not the values that they are assigned to. Somehow multiply calling add doesn't return an error, even though add is declared below multiply.







javascript function scope hoisting lexical






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 9 at 1:40







Hadoren

















asked Mar 9 at 1:01









HadorenHadoren

82210




82210












  • I think so, based on my admittedly flawed memory of reading this blog.bitsrc.io/…, which might teach you more than you wanted to know. The basics I remember include that each function gets its own execution context which includes a couple of internal lexical environments (one of which is specific to those identifiers declared with var) and these lexical environments can access the outer environment. Also, I think var and function declarations get hoisted but let and const declarations don't...

    – Cat
    Mar 9 at 1:32











  • The explanation is pretty simple. JS lets your functions reference variables that don't exist. So the potential for error only comes after the function is invoked. At the time of invocation, if the referenced variable doesn't exist, you get an error. As a test, remove the add() function, and update multiply() so that it uses a try/catch, where the try tries to call add(), and the catch creates it at window.add = function() .... You'll see that the ReferenceError is caught on the first invocation, but subsequent invocations succeed.

    – ziggy wiggy
    Mar 9 at 1:50












  • ...like this: jsfiddle.net/cpzj309w

    – ziggy wiggy
    Mar 9 at 1:53

















  • I think so, based on my admittedly flawed memory of reading this blog.bitsrc.io/…, which might teach you more than you wanted to know. The basics I remember include that each function gets its own execution context which includes a couple of internal lexical environments (one of which is specific to those identifiers declared with var) and these lexical environments can access the outer environment. Also, I think var and function declarations get hoisted but let and const declarations don't...

    – Cat
    Mar 9 at 1:32











  • The explanation is pretty simple. JS lets your functions reference variables that don't exist. So the potential for error only comes after the function is invoked. At the time of invocation, if the referenced variable doesn't exist, you get an error. As a test, remove the add() function, and update multiply() so that it uses a try/catch, where the try tries to call add(), and the catch creates it at window.add = function() .... You'll see that the ReferenceError is caught on the first invocation, but subsequent invocations succeed.

    – ziggy wiggy
    Mar 9 at 1:50












  • ...like this: jsfiddle.net/cpzj309w

    – ziggy wiggy
    Mar 9 at 1:53
















I think so, based on my admittedly flawed memory of reading this blog.bitsrc.io/…, which might teach you more than you wanted to know. The basics I remember include that each function gets its own execution context which includes a couple of internal lexical environments (one of which is specific to those identifiers declared with var) and these lexical environments can access the outer environment. Also, I think var and function declarations get hoisted but let and const declarations don't...

– Cat
Mar 9 at 1:32





I think so, based on my admittedly flawed memory of reading this blog.bitsrc.io/…, which might teach you more than you wanted to know. The basics I remember include that each function gets its own execution context which includes a couple of internal lexical environments (one of which is specific to those identifiers declared with var) and these lexical environments can access the outer environment. Also, I think var and function declarations get hoisted but let and const declarations don't...

– Cat
Mar 9 at 1:32













The explanation is pretty simple. JS lets your functions reference variables that don't exist. So the potential for error only comes after the function is invoked. At the time of invocation, if the referenced variable doesn't exist, you get an error. As a test, remove the add() function, and update multiply() so that it uses a try/catch, where the try tries to call add(), and the catch creates it at window.add = function() .... You'll see that the ReferenceError is caught on the first invocation, but subsequent invocations succeed.

– ziggy wiggy
Mar 9 at 1:50






The explanation is pretty simple. JS lets your functions reference variables that don't exist. So the potential for error only comes after the function is invoked. At the time of invocation, if the referenced variable doesn't exist, you get an error. As a test, remove the add() function, and update multiply() so that it uses a try/catch, where the try tries to call add(), and the catch creates it at window.add = function() .... You'll see that the ReferenceError is caught on the first invocation, but subsequent invocations succeed.

– ziggy wiggy
Mar 9 at 1:50














...like this: jsfiddle.net/cpzj309w

– ziggy wiggy
Mar 9 at 1:53





...like this: jsfiddle.net/cpzj309w

– ziggy wiggy
Mar 9 at 1:53












1 Answer
1






active

oldest

votes


















1














You are correct in that the declarations are hoisted to the top, while the assignments are not.



However, functions don't keep the values of any variables outside of them from when they are created. Instead, they use whatever is in them when they are called. In this case, add is undefined when the multiply function is created, but is assigned a function before multiply is called, so multiply uses the new assigned function.



To see this more clearly, consider this code:






var multiply = function(num) 
return add(num) * 2;
;

// Would be an error
// console.log(multiply(1));

var add = function(num)
return num + 1;
;

console.log(multiply(1)); // Prints 4

add = function(num)
return num + 2;
;

console.log(multiply(1)); // Prints 6





The last console.log prints 6 because multiply used the new function in add instead of keeping the one it had before.






share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55072977%2fjavascript-hoisting-function-can-refer-to-another-function-declared-below-it%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    You are correct in that the declarations are hoisted to the top, while the assignments are not.



    However, functions don't keep the values of any variables outside of them from when they are created. Instead, they use whatever is in them when they are called. In this case, add is undefined when the multiply function is created, but is assigned a function before multiply is called, so multiply uses the new assigned function.



    To see this more clearly, consider this code:






    var multiply = function(num) 
    return add(num) * 2;
    ;

    // Would be an error
    // console.log(multiply(1));

    var add = function(num)
    return num + 1;
    ;

    console.log(multiply(1)); // Prints 4

    add = function(num)
    return num + 2;
    ;

    console.log(multiply(1)); // Prints 6





    The last console.log prints 6 because multiply used the new function in add instead of keeping the one it had before.






    share|improve this answer





























      1














      You are correct in that the declarations are hoisted to the top, while the assignments are not.



      However, functions don't keep the values of any variables outside of them from when they are created. Instead, they use whatever is in them when they are called. In this case, add is undefined when the multiply function is created, but is assigned a function before multiply is called, so multiply uses the new assigned function.



      To see this more clearly, consider this code:






      var multiply = function(num) 
      return add(num) * 2;
      ;

      // Would be an error
      // console.log(multiply(1));

      var add = function(num)
      return num + 1;
      ;

      console.log(multiply(1)); // Prints 4

      add = function(num)
      return num + 2;
      ;

      console.log(multiply(1)); // Prints 6





      The last console.log prints 6 because multiply used the new function in add instead of keeping the one it had before.






      share|improve this answer



























        1












        1








        1







        You are correct in that the declarations are hoisted to the top, while the assignments are not.



        However, functions don't keep the values of any variables outside of them from when they are created. Instead, they use whatever is in them when they are called. In this case, add is undefined when the multiply function is created, but is assigned a function before multiply is called, so multiply uses the new assigned function.



        To see this more clearly, consider this code:






        var multiply = function(num) 
        return add(num) * 2;
        ;

        // Would be an error
        // console.log(multiply(1));

        var add = function(num)
        return num + 1;
        ;

        console.log(multiply(1)); // Prints 4

        add = function(num)
        return num + 2;
        ;

        console.log(multiply(1)); // Prints 6





        The last console.log prints 6 because multiply used the new function in add instead of keeping the one it had before.






        share|improve this answer















        You are correct in that the declarations are hoisted to the top, while the assignments are not.



        However, functions don't keep the values of any variables outside of them from when they are created. Instead, they use whatever is in them when they are called. In this case, add is undefined when the multiply function is created, but is assigned a function before multiply is called, so multiply uses the new assigned function.



        To see this more clearly, consider this code:






        var multiply = function(num) 
        return add(num) * 2;
        ;

        // Would be an error
        // console.log(multiply(1));

        var add = function(num)
        return num + 1;
        ;

        console.log(multiply(1)); // Prints 4

        add = function(num)
        return num + 2;
        ;

        console.log(multiply(1)); // Prints 6





        The last console.log prints 6 because multiply used the new function in add instead of keeping the one it had before.






        var multiply = function(num) 
        return add(num) * 2;
        ;

        // Would be an error
        // console.log(multiply(1));

        var add = function(num)
        return num + 1;
        ;

        console.log(multiply(1)); // Prints 4

        add = function(num)
        return num + 2;
        ;

        console.log(multiply(1)); // Prints 6





        var multiply = function(num) 
        return add(num) * 2;
        ;

        // Would be an error
        // console.log(multiply(1));

        var add = function(num)
        return num + 1;
        ;

        console.log(multiply(1)); // Prints 4

        add = function(num)
        return num + 2;
        ;

        console.log(multiply(1)); // Prints 6






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 9 at 1:54









        VLAZ

        5,10742235




        5,10742235










        answered Mar 9 at 1:08









        NicholasNicholas

        30619




        30619





























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55072977%2fjavascript-hoisting-function-can-refer-to-another-function-declared-below-it%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Identity Server 4 is not redirecting to Angular app after login2019 Community Moderator ElectionIdentity Server 4 and dockerIdentityserver implicit flow unauthorized_clientIdentityServer Hybrid Flow - Access Token is null after user successful loginIdentity Server to MVC client : Page Redirect After loginLogin with Steam OpenId(oidc-client-js)Identity Server 4+.NET Core 2.0 + IdentityIdentityServer4 post-login redirect not working in Edge browserCall to IdentityServer4 generates System.NullReferenceException: Object reference not set to an instance of an objectIdentityServer4 without HTTPS not workingHow to get Authorization code from identity server without login form

            2005 Ahvaz unrest Contents Background Causes Casualties Aftermath See also References Navigation menue"At Least 10 Are Killed by Bombs in Iran""Iran"Archived"Arab-Iranians in Iran to make April 15 'Day of Fury'"State of Mind, State of Order: Reactions to Ethnic Unrest in the Islamic Republic of Iran.10.1111/j.1754-9469.2008.00028.x"Iran hangs Arab separatists"Iran Overview from ArchivedConstitution of the Islamic Republic of Iran"Tehran puzzled by forged 'riots' letter""Iran and its minorities: Down in the second class""Iran: Handling Of Ahvaz Unrest Could End With Televised Confessions""Bombings Rock Iran Ahead of Election""Five die in Iran ethnic clashes""Iran: Need for restraint as anniversary of unrest in Khuzestan approaches"Archived"Iranian Sunni protesters killed in clashes with security forces"Archived

            Can't initialize raids on a new ASUS Prime B360M-A motherboard2019 Community Moderator ElectionSimilar to RAID config yet more like mirroring solution?Can't get motherboard serial numberWhy does the BIOS entry point start with a WBINVD instruction?UEFI performance Asus Maximus V Extreme