Home/ Questions/Q 8501483
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T01:13:30+00:00

1. >>> const a = 2 2. >>> var a = 3 3. >>>

  • 0
1. >>> const a = 2
2. >>> var a = 3
3. >>> a = 4
4. >>> a // print 2

Why the operation line 3 is allowed? const seems more “global” than without any keyword…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is is just how const works (or doesn’t work):

    Creates a constant1 that can be global or local to the function in which it is declared. Constants follow the same scope rules as variables [.. and cannot share a name] with a function or a variable in the same scope.

    Firefox [..] throws a TypeError if you redeclare2 [which is different than re-assigning] a constant. None of the major browsers produce any notices or errors2,3 if you assign another value to a constant [..] but the reassignment is unsuccessful (only) in Firefox and Chrome (at least since version 20).

    Note that const is not part of the ECMAScript 5 specification and the JavaScript 1.5 semantics will be re-defined in ECMAScript 6.

    Behavior will vary across browser implementations with respect to support and re-declaration/re-assignments semantics.

    1 In IE 9, using const a = 2 results in

    "Syntax error"

    2 In FF 14, const a = 2; var a = 3; a = 4; a, when evaluated as a single program, results in

    TypeError: redeclaration of const a

    which is different than executing each line one-at-a-time in the REPL. I suspect this is because var is hoisted above the const and because a const "cannot share a name with a function or variable in the same scope".

    3 In Chrome 21, const a = 2; var a = 3; a = 4; a evaluates to 2 with no warning or message.

    • 0