Today on the serverjs mailing list, the subject of standardizing
debugging interfaces came up.
http://is.gd/WmuI
As Mark notes in his post on the thread, something on the level of
JPDA (JDI et al), or the more "modern" JVMTI (http://java.sun.com/javase/6/docs/technotes/guides/jvmti/
) might be the sort of things to target, in terms of functionality.
I also noticed Charles McCaffieNevile mentioned standardized debugging
API in a movie recently placed up on Yahoo Theatre (at about 14:50):
http://developer.yahoo.com/yui/theater/mccathienevile-dragonfly.html
On a somewhat related note, there has been some work making the
debugging experience better for developers, by making use of some non-
standard conventions in source code. Two of these I'm familiar with
are FireFox's "//@ sourceURL" annotation to 'name' eval() and
Function() code blocks, and WebKit's displayName property to name
otherwise anonymous functions. In both of these cases, the
functionality is provided purely for the use of developer tooling -
debugging and profiling. Links to more info on these here:
http://pmuellr.blogspot.com/2009/06/debugger-friendly.html
I've run into a few people interested in looking into this, but it's
not quite clear to me where work relating to this should happen. I
tend to view standards groups as not the places to do design work, so
didn't really think ECMA would be the right place to talk about this,
but Mark Miller indicated it would be good to at least post the
thought up here.
So, question is, where might folks interesting in this stuff work on
this? Here? I was also thinking the nascent Open Web Advocacy group
might be another place:
http://groups.google.com/group/openweb-group
Patrick Mueller - http://muellerware.org/
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
