The current debugging mechanism is not particularly pleasant to use, nor is it very future proof, it has significant performance costs, and it requires the user to have significant knowledge of the inner workings of JSC.
Before we started considering exposing JS debugging through API (and therefore introducing additional binary compatibility requirements) we would need to have an improved debugging mechanism that resolved these issues. --Oliver On Jun 14, 2011, at 7:38 AM, demallien wrote: > Hi, > > I'm interested in providing a public C API for accessing debugger > functionality in JavascriptCore. Ideally I would like the code to be merged > into webkit, so I wanted to know if there is a policy reason for not already > having debugger APIs available in the public JavascriptCore APIs? If so, my > work will obviously not be compatible with the policy, and I won't bother > trying to conform to webkit coding standards, as the code will clearly not be > accepted into webkit. Othwerwise I'll make an effort to make it fit in with > the rest of the system. > > So, is there a reason for there not being a publically accessible debugger > API? > > Alli > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
