On Fri, Dec 20, 2013 at 2:25 PM, Dean Landolt <[email protected]> wrote:
> > > > On Fri, Dec 20, 2013 at 2:14 PM, Andrea Giammarchi < > [email protected]> 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. > Sorry, just getting caught up here... These points are the basis of my "invalid comparison" claim. Rick
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
