domenic at domenicdenicola.com (2014-01-06T13:51:53.058Z)
As written above this couldn't possibly work in C -- const is block level, right? Originally you wrote this with #ifdefs, which aren't blocks. This isn't even close to apples-to-apples. So are you suggesting that js grow a preprocessor? That block scoping shouldn't *really* mean block scoping? Or that const shouldn't *really*mean const? Best I can tell it could only be one of those three -- and they all sound bad to me.
On Fri, Dec 20, 2013 at 2:14 PM, Andrea Giammarchi < andrea.giammarchi at gmail.com> wrote: > This is not helping ... yeah, apples-to-orange, as you wish .. now to > imagine you have a flexible understanding of the issue and the example I > was proposing so that: > > if (stuff) { > const WHATEVER = 1; > } else { > const WHATEVER = 2; > } > > two blocks, one const assigned with possibly only one value > > Now tell me again how this works in C ... > As written above this couldn't possibly work in C -- const is block level, right? Originally you wrote this with #ifdefs, which aren't blocks. This isn't even close to apples-to-apples. So are you suggesting that js grow a preprocessor? That block scoping shouldn't *really* mean block scoping? Or that const shouldn't *really*mean const? Best I can tell it could only be one of those three -- and they all sound bad to me. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131220/f28bd508/attachment.html>