mozilla / spiderflunky

Static analysis of JavaScript
5 stars 3 forks source link

Tern #18

Closed mvcisback closed 10 years ago

mvcisback commented 10 years ago

Should give us #14, #8, and and a start torwards #7 (I would just include it, but the call_sites code may have some subtle edge cases since we interact with the server, and would thus need to keep that information overhead).

erikrose commented 10 years ago

IRC transcript:

ErikRose: Getting back to your original question...assuming the tern approach yields a reasonable take on moz-central, I think the tern thing should be a separate project. ErikRose: There's nothing left of spiderflunky in your tern branch, so there's nothing to be shared—no common abstractions or shared code ErikRose: And, since we might return to a Spindermonkey-based thing later, we shouldn't obliterate it. marcell: yep, thats how felt as well ErikRose: I'm not even sure whether it needs to be a separate lib. That's up to you. Myself, I'd probably just suck it into a DXR plugin and factor it out if and when we want to use it somewhere else. marcell: ok ErikRose: Since tern does most of the work, it's just that one 200-line module