Le 03/04/2012 17:12, John J Barton a écrit :
On Tue, Apr 3, 2012 at 7:03 AM, David Bruant <bruan...@gmail.com
<mailto:bruan...@gmail.com>> wrote:
Le 01/04/2012 13:38, Wes Garland a écrit :
In a similar vein, I would personally like to have
zero-cost-when-not-debugging assert() statements, and am
hopeful that statically-linked modules might lead the way.
It seems to me that what you're asking for is macros, isn't it?
I read hints here and there that it's a very hard problem that is
being worked on for a later ES version.
Since most JS is compiled in the run time, macros are not zero cost.
Wes mentionned:
"As a data point, we compile all our code through Mozilla's SpiderMonkey
engine with JSOPTION_STRICT, which pre-dates ES5 strict mode, during our
build phase."
It seems to me that it would be equivalent work to remove macros with
such a compilation phase, making the macro cost effectively zero in
run-time phase.
Since most JS runs in a sophisticated JIT capable of dead code
elimination,
const debug = false;
Macros would probably also be less intrusive than a top-scope variable,
but I may be wrong on this part.
David
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
