It sounds like you want a standardized debugger and profiler API, rather than a language feature. Every engine is different enough internally that I don't think it makes sense to have a standardized debugger API.
That said, the Mozilla Debugger API is quite impressive. It might make sense to look at standardizing a subset of that. On Mon, Sep 29, 2014 at 2:20 AM, Andreas Rossberg <[email protected]> wrote: > On 28 September 2014 20:34, Michał Wadas <[email protected]> wrote: > > We have Object.observe (asynchronous callback whenever object > > properties changes), but do we need Function.observe (asynchronous > > callback whenever function is called)? > > > > Cons: > > - can prevent many optimizations (but Object.observe too) > > > > Pros: > > - allows easy debugging and profiling > > - allows extending libraries functionalities without modyfing their > > code (widgets?) > > > > What should be eventually received by callback code? Possible options: > > - arguments (can prevent certain optimizations; critical for debugging > > and profiling) > > - caller > > - callee > > - function's execution time > > - thisArg of observed function (critical for observing methods of > prototype) > > Won't happen. This would be a _gigantic_ encapsulation leak, and is > bound to cause security issues without end. > > /Andreas > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > -- Jasper
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
