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 ...
On Fri, Dec 20, 2013 at 10:38 AM, J B <por...@gmail.com> wrote:
> As far as the compiler is concerned it is only defined once. The
> preprocessor strips the second const out before the compilation phase.
>
> Let me correct my earlier statement: "Your C comparison was
> apples-to-oranges, #ifdef is evaluated before compilation."
>
>
> On Fri, Dec 20, 2013 at 1:02 PM, Andrea Giammarchi <
> andrea.giammar...@gmail.com> wrote:
>
>> many launches --harmony by default with node, many others surf the web on
>> the edge. I don't want to tell anyone what to do in order to use a library,
>> they know experimental is experimental, and as Developer I would like to be
>> able to feature-detect experiments or at least know that I am in an
>> experimental Environment.
>>
>> Once again, this is off-topic here, but Proxy is a very good example for
>> this problem, so are generators in older Spidermonkey versions, so are ...
>> you name it, avoiding vendor prefixes for not finalized yet stuff is a hell
>> of a foot-gun for both specifications and developers ... maybe we don't see
>> this as a problem today, even if there are already concrete examples like
>> this, but I am sure it will come back soon.
>>
>>
>> On Fri, Dec 20, 2013 at 3:05 AM, Claude Pache <claude.pa...@gmail.com>wrote:
>>
>>>
>>> Le 20 déc. 2013 à 08:36, Andrea Giammarchi <andrea.giammar...@gmail.com>
>>> a écrit :
>>>
>>> > as side note: in node.js using --harmony flag ... what a developer
>>> should do there to understand that a partially non standard version of
>>> Proxy is there instead of the real one?
>>> >
>>> > Let's imagine I am a client/server library author ... just for a
>>> second, I'd like to grant one behaviour across platforms ... I'd love V8 to
>>> flag experimental features as v8Proxy instead, at least I know what I am
>>> dealing with!!! Don't care about multiple checks, as long as I can grant
>>> consistency.
>>> >
>>> > This is a concern of mine that keeps coming up ... off topic here
>>> >
>>>
>>> Surely not the answer you want, but as developer, I would consider the
>>> following actions:
>>>
>>> * Putting a prominent warning in my library doc: Do not use outdated
>>> builds with experimental features enabled. It would make babies cry.
>>> * Opening a bug against implementations, asking that builds with
>>> experimental features enabled must have an expiration date. It may annoy
>>> users, but at least, it will prevent kitten from being killed.
>>>
>>> —Claude
>>
>>
>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss@mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
>>
>
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
