Very easy to avoid if you're compiling a statically typed language to JS.
> No integers
Not in the JS specification (outside typed arrays), but every JS JIT works in a way you can actually declare variables as 32 bit signed integers, and made its way into the asm.js specification. They are declared like this:
var a = value|0;
Where the |0 is a no-op so not actually done, just a type hint.
If what worries you is precision and not performance, doubles allow 53 bit integers (not counting sign bit) with full precision.
> Say you have a demo page for some language, and someone using the page writes an infinite loop. Don't want the page to crash? Welcome to advanced compilation techniques like CPS transformations and trampolining.
Or just use a web worker, which you can terminate if you haven't heard back in a while (pun intended).
> and any part of the language you target for which you don't fully understand the spec is a potential bug
It heavily depends on what type of language you do. If your compiler tracks the types and doesn't mix them, edge cases are much, much easier to avoid.
Source: I did make a compiler for my own language that targeted JS.
>Not in the JS specification (outside typed arrays), but every JS JIT works in a way you can actually declare variables as 32 bit signed integers, and made its way into the asm.js specification. They are declared like this:
The "|0" trick you mention is not for javascript; it is for asm.js; to be able to declare such a "true integer" variable, your code would need to be in asm.js, not javascript.
Javascript has no integers, only floating point numbers. This is a very strong limitation.
When JS is a compiler target, that truck will generally only be used if the source language excludes all those edge cases, i.e. the value is guaranteed to be an integer.
Very easy to avoid if you're compiling a statically typed language to JS.
> No integers
Not in the JS specification (outside typed arrays), but every JS JIT works in a way you can actually declare variables as 32 bit signed integers, and made its way into the asm.js specification. They are declared like this:
Where the |0 is a no-op so not actually done, just a type hint.If what worries you is precision and not performance, doubles allow 53 bit integers (not counting sign bit) with full precision.
> Say you have a demo page for some language, and someone using the page writes an infinite loop. Don't want the page to crash? Welcome to advanced compilation techniques like CPS transformations and trampolining.
Or just use a web worker, which you can terminate if you haven't heard back in a while (pun intended).
> and any part of the language you target for which you don't fully understand the spec is a potential bug
It heavily depends on what type of language you do. If your compiler tracks the types and doesn't mix them, edge cases are much, much easier to avoid.
Source: I did make a compiler for my own language that targeted JS.