Andrew
Schorn, Markus wrote:
This is great start! In addition to your proposal it would be
useful to (optionally) run some (or all?) of the checkers on the
editor every time the user stops
typing.
The editor creates an AST at this point of time anyways, so as
long as
there are simple checkers this should not add a noteable
performance overhead.
Markus.
-----Original Message-----
From:
cdt-dev-bounces@xxxxxxxxxxx
<mailto:
cdt-dev-bounces@xxxxxxxxxxx>
[mailto:
cdt-dev-bounces@xxxxxxxxxxx
<mailto:
cdt-dev-bounces@xxxxxxxxxxx>] On Behalf Of Elena
Laskavaia
Sent: Monday, April 20, 2009 4:51 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Static Analysis Framework for CDT
Importance: Low
There is not much of this "framework" can be re-used for
self contained external tool like that.
I don't think even error parser is required because it would
just work with gcc error parser, so it would pretty much
work out of box considering integration is provided by
makefile (which should be done anyway on make/build level
and not invoked externally)
Btw, I am pretty much done with preliminary framework
(without data-flow graphs etc), I update wiki page
http://wiki.eclipse.org/CDT/designs/StaticAnalysis
added screenshots for user interface, comments are welcome.
I have 2 checkers now Assignment in Condition from Markus
presentation and Statement has no Effect.
Checkers contributions are welcome. We need at least dozen
checkers to make it worthy to include as feature in next CDT.
Schaefer, Doug wrote:
That sounds reasonable. I'm still concerned about the
licensing issues
with the GCC plug-in framework, but we're starting to
figure out how
to manage that with the packaging efforts.
Cheers,
Doug.
-----Original Message-----
From:
cdt-dev-bounces@xxxxxxxxxxx
<mailto:
cdt-dev-bounces@xxxxxxxxxxx>
[mailto:
cdt-dev-bounces@xxxxxxxxxxx