A response to Andrew, and then some new features for you to try...
I see two simple-ish solutions:
1) Modify the preprocessor to log a concise line mapping (naming the
This is an interesting idea. Benjamin was suggesting I think about
adding my xpidl_xref patch to the tree too. I've been trying to make
this code usable on boxes other than mine, and all the stupid build
system tricks I have to do make it hard.
2) Only process the preprocessed code. Preprocessed javascript code is
largely a dumb idea and there is almost no good reason for it. There is
no need to cater to that usage, and this will encourage people to
abandon it.
Dumb or no, I think I have to do it, since people will expect there to
be info for all files
...
In addition to working on a source release (hopefully next week), I took
a stab at adding an outline view to the current file. Taras mentioned
that he's been wanting to see a top-level view of what's in the current
file. My current UI isn't perfect yet, but it adds some interesting
navigation.
I regenerated the html for the tree, so you can use it at:
http://scotland.proximity.on.ca/dxr/search.html
Here are some examples:
* Simple .cpp -
http://scotland.proximity.on.ca/dxr/mozilla-central/accessible/src/html/nsHTMLImageAccessible.cpp.html
* Complex .cpp -
http://scotland.proximity.on.ca/dxr/mozilla-central/rdf/base/src/nsRDFService.cpp.html
* .h file -
http://scotland.proximity.on.ca/dxr/mozilla-central/accessible/src/html/nsHTMLImageAccessible.h.html
* .idl file (NOTE: looks like I'm reporting line+1 in a lot of cases for
idl)
http://scotland.proximity.on.ca/dxr/mozilla-central/accessible/public/nsIAccessible.idl.html
As you look at files, you'll quickly hit things that aren't compiled in
a Linux build, and therefore have no dehydra data.
Doing this I also see that I'm missing globals and static members. TODO.
Having this navigation in place motivates me to get decl to def and/or
callers working: if you're in a .h or .idl file, you should be able to
get to the implementation(s) and users somehow. I'm struggling with the
UI for this, so ideas welcome.
Finally, as I add more awesome-sauce, I'm feeling the dom load/lag more
and more. I'll be interested to get some smart people to help me think
through this moving forward.
Dave
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
