oliver at apple.com
Tue Jun 14 09:21:48 PDT 2011
It depends on what you mean by "official"
I would probably r- any patch that attempted to create such an API, but it's conceivable that a sensible API could be made that masked the current craziness sufficiently to allow the craziness to be removed later. But any API would need to be very carefully thought out, and would probably require multiple iterations to get to the point where we'd consider the API sufficiently good.
On Jun 14, 2011, at 9:12 AM, demallien wrote:
> Is that an official response?
> On 14 Jun, 2011,at 06:03 PM, Oliver Hunt <oliver at apple.com> wrote:
>> 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.
>> On Jun 14, 2011, at 7:38 AM, demallien wrote:
>> > Hi,
>> > So, is there a reason for there not being a publically accessible debugger API?
>> > Alli
>> > _______________________________________________
>> > webkit-dev mailing list
>> > webkit-dev at lists.webkit.org
>> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev