The API I've proposed is open-ended in that it's possible to extend the type enum and the events structure in a backwards-compatible way, so it should be extendible to the interface you desire. Enumerating existing code sounds like a good idea, but it's not necessary for the use case I'm looking to implement. I suggest we land my change and build on it?
On Tue, Jul 31, 2012 at 9:07 AM, <[email protected]> wrote: > Henry Rawas (Node.js project) also has been working on a similar API. > > What we would need is a way to enumerate existing code locations as well. > If you > are going to land this patch, would it be possible to support this? > > For your reference, this was the API we were going to propose: > http://codereview.chromium.**org/10837021/patch/1/2<http://codereview.chromium.org/10837021/patch/1/2> > > Thanks, > -Bert > > https://chromiumcodereview.**appspot.com/10795074/<https://chromiumcodereview.appspot.com/10795074/> > -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
