Bug 23559 - Conformance check system
Summary: Conformance check system
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-codan (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: CDT Codan Inbox CLA
QA Contact: Elena Laskavaia CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-13 09:25 EDT by Xavier Méhaut CLA
Modified: 2014-11-28 15:28 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Méhaut CLA 2002-09-13 09:25:47 EDT
Hello,
(still me :-( )
In an industry targeted purpose, it could be good to propose to the developper 
a system which enables him to check if his code is conform or not to pre-
established rules. I've in mind especially rules which could derive from 
standards applied in industry like DO178B, PSS05, OSEK, and so on... A simple 
example, in such standards, dynamic allocation is forbidden... such a thing 
could be checked...
documentation associated is important too in this work frame. The customer area 
of CDT is certainly quite diffrent from the java, or cobol one.
regards
Xavier
Comment 1 Kleo Hapitas CLA 2004-07-07 16:52:44 EDT
PR was not targeted to any particular release. Changing target milestone to 2.1
Comment 2 Alain Magloire CLA 2004-11-04 09:48:53 EST
Xavier .. you have excellent ideas.
We just lack the resources to implement them ... at least for now.

Please keep them coming though.
Comment 3 Doug Schaefer CLA 2006-12-04 21:45:36 EST
TPTP static analysis is ready to do things like this. We should do an example to show how.
Comment 4 Doug Schaefer CLA 2007-08-21 10:55:04 EDT
Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'.
Comment 5 Andrew Gvozdev CLA 2011-03-04 10:01:17 EST
changing category to codan
Comment 6 Elena Laskavaia CLA 2014-11-28 15:28:29 EST
Would be a good project for google code of summer student