28236 2009-08-12 15:47:31 -0700 Eval doesn't respect JavaScript's const keyword 2012-03-07 00:32:49 -0800 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) All All RESOLVED DUPLICATE 31813 P2 Normal --- 1 joepeck webkit-unassigned aroben barraclough kmccullough oliver timothy oldest_to_newest 139615 0 joepeck 2009-08-12 15:47:31 -0700 It seems a const variable declared in the Console is just a "var" and can change value. > zzz // ensure it doesn't exist ReferenceError: Can't find variable: zzz > const zzz = 10; undefined > zzz = 5; // should do nothing 5 > zzz 5 I would have expected the result to have been 10, since the constant shouldn't change. 139620 1 joepeck 2009-08-12 15:54:30 -0700 Maybe this is actually a problem with eval(): Expected Behavior without eval: javascript:const zza = 10; zza = 5; alert(zza) => 10 Bad Behavior with eval: javascript:alert(eval("const zzb = 10; zzb = 5; zzb")) => 5 How should this bug be reclassified? 139672 2 timothy 2009-08-12 17:18:14 -0700 Oliver, thoughts? 139673 3 oliver 2009-08-12 17:20:49 -0700 Yeah this is a known bug with eval 572646 4 barraclough 2012-03-07 00:32:49 -0800 We should resolved this by implementing ES Harmony block scoped const. *** This bug has been marked as a duplicate of bug 31813 ***