[Bug 68610] New: Enhance problem reporter for more advanced analysis

[Jesse Yurkovich]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=68610     
           Summary: Enhance problem reporter for more advanced analysis
           Product: kdevelop
           Version: 3.0.0b1
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: yurkjes at iit.edu


Version:           3.0.0b1 (using KDE Devel)
Installed from:    Compiled sources
OS:          Linux

Enhancing the problem reporter with the following additions will make it infinitly more useable.  (cpp problem reporter)

- Report unused vars and parameters (obvious)

- Vars that have not been declared within scope should be marked
  If I try to use var1 and I haven't declared it yet (or maybe misspelled it) should be indicated

- Invalid method invocations
  Currently if I have obj.do_stuff (); it reports no error (syntactically correct) but method do_stuff () does not exist :(

- Use of deprecated API
  Even though a properly deprecated method in gcc will trigger an output warning upon compilation, it might be good to also report the problem as well

- Problem reporter is too strict and interferes with rest of code
  This is a side affect of the c language in that one misplaced ; will result in hundreds of weird errors.  Perhaps the reporter should try to go line-at-a-time (using some context of course) to prevent the reporter from generating 10 useless errors from one misplaced ;

** Use new arbitrary highlighter to mark the problems in the editor as well
as in the reporter view.

I do a little development with Kate and there's been some talk of creating an arbitrary highlighter so smart applications like KDevelop and Quanta can instruct the editor to highlight certain parts of text in a certain style.
Think: var1 is undeclared so KDevelop tells Kate to highlight var1 so it has squiggly red marks under the name. (akin to red squiggly marks under misspelled text in a word processor)

Think: KDevelop knows all classes within a project.  It can tell Kate to highlight all declaration of the form Class var; so Class is highlighted differently.  The same with method calls and attributes (currently statically highlighted through the Kate syntax defs which isn't too nice)