Closed Bug 732442 Opened 13 years ago Closed 12 years ago

Add parser support to the debugger for lookup of references to function names, variables, etc

Categories

(DevTools :: Debugger, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 762160

People

(Reporter: rcampbell, Unassigned)

References

(Blocks 1 open bug)

Details

We should add a parser to the source editor to provide support for doing lookups (references, implementors, sends), flagging errors and other general awesomeness with code. I'm currently not sure if we want to do this in the source editor itself or in the debugger. I can think of good reasons to have it in both locations or access to a central script container that can do these types of lookups for us. Should probably use the SpiderMonkey Parser API for this. https://developer.mozilla.org/en/SpiderMonkey/Parser_API
Priority: -- → P3
(In reply to Rob Campbell [:rc] (:robcee) from comment #0) > We should add a parser to the source editor to provide support for doing > lookups (references, implementors, sends), flagging errors and other general > awesomeness with code. > > I'm currently not sure if we want to do this in the source editor itself or > in the debugger. I can think of good reasons to have it in both locations or > access to a central script container that can do these types of lookups for > us. > > Should probably use the SpiderMonkey Parser API for this. > > https://developer.mozilla.org/en/SpiderMonkey/Parser_API I think we should do it in the source editor. This way, we can reuse those methods everywhere, should we need 'em.
(bug 725399 would be the first thing to do, bug 732442 should follow)
This starts feeling like a meta bug :)
could be.
Patch in bug 762160 contains a Parser.jsm for the purpose of this bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.