Allen Wirfs-Brock wrote:
It isn't clear to me that there is much difference between an invocation-fused explosive function-level and a similarly fused script file or module. The triggering of each of these normally occurs at some point after some application code has executed to even if we are talking about ES5 "early errors" they are occuring at runtime and may be trigger by some sort of invocation-like action.
No, there's a difference, Mark talked about it clearly at the meeting last week: the all-or-nothing early error property ensures that the heap is not littered with landmines. The poisoned function alternative is exactly that: a heap paved in mines.
/be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
