digitalmars.D.bugs - [Issue 4480] New: JSON: include location range, not just line numbers, for everything
- d-bugmail puremagic.com (28/28) Jul 17 2010 http://d.puremagic.com/issues/show_bug.cgi?id=4480
- d-bugmail puremagic.com (12/12) Feb 23 2012 http://d.puremagic.com/issues/show_bug.cgi?id=4480
http://d.puremagic.com/issues/show_bug.cgi?id=4480 Summary: JSON: include location range, not just line numbers, for everything Product: D Version: D1 & D2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: DMD AssignedTo: nobody puremagic.com ReportedBy: dhasenan gmail.com --- If you include the location range for everything in the json output, it's much easier to implement navigate-to-declaration in an IDE. For example, if there is code: logger.trace(...); json only outputs "line": 18. But if it instead put: "range": { "start": {"line": 18, "col": 4}, "end": {"line": 18, "col": 16}} Then it's easier for an IDE to find the identifier under the cursor. Similarly, IDEs often allow you to "fold" code -- collapse a declaration so you don't have to see it, or collapse a function body or a block. Including a range means the IDE doesn't need to parse D. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Jul 17 2010
http://d.puremagic.com/issues/show_bug.cgi?id=4480 Matt Peterson <revcompgeek gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |revcompgeek gmail.com PST --- DMD doesn't currently store line offset information, so this is a fairly invasive enhancement to do, although I agree it would be very nice to have this. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
Feb 23 2012