# HG changeset patch # User dan.podwall@nokia.com # Date 1239047788 18000 # Node ID 887bd61e1328fa9b4e344a5d00efb25e254cfa62 # Parent ff58688cad6c081c069692c7ee5355691f703d8e# Parent 8254273d11c07d9f3ed06c53c5f43735f150a6be merge from RCL_2_0 to default diff -r 8254273d11c0 -r 887bd61e1328 .branch.txt --- a/.branch.txt Mon Apr 06 14:33:24 2009 -0500 +++ b/.branch.txt Mon Apr 06 14:56:28 2009 -0500 @@ -1,1 +1,1 @@ -RCL_2_0 +default diff -r 8254273d11c0 -r 887bd61e1328 .hgignore --- a/.hgignore Mon Apr 06 14:33:24 2009 -0500 +++ b/.hgignore Mon Apr 06 14:56:28 2009 -0500 @@ -1,6 +1,5 @@ # use glob syntax. syntax: glob -*.class bin runtime \.DS_Store diff -r 8254273d11c0 -r 887bd61e1328 builder/com.nokia.carbide.cdt.builder.test/src/com/nokia/carbide/cdt/builder/test/errorParsers/AllTests.java --- a/builder/com.nokia.carbide.cdt.builder.test/src/com/nokia/carbide/cdt/builder/test/errorParsers/AllTests.java Mon Apr 06 14:33:24 2009 -0500 +++ b/builder/com.nokia.carbide.cdt.builder.test/src/com/nokia/carbide/cdt/builder/test/errorParsers/AllTests.java Mon Apr 06 14:56:28 2009 -0500 @@ -27,6 +27,7 @@ //$JUnit-BEGIN$ suite.addTestSuite(TestRVCTErrorParser.class); suite.addTestSuite(TestMakmakeErrorParser.class); + suite.addTestSuite(TestSBSv2ErrorParser.class); //$JUnit-END$ return suite; } diff -r 8254273d11c0 -r 887bd61e1328 core/carbide_releases/readme/background_carbide.jpg Binary file core/carbide_releases/readme/background_carbide.jpg has changed diff -r 8254273d11c0 -r 887bd61e1328 core/carbide_releases/readme/readme_sdks.html --- a/core/carbide_releases/readme/readme_sdks.html Mon Apr 06 14:33:24 2009 -0500 +++ b/core/carbide_releases/readme/readme_sdks.html Mon Apr 06 14:56:28 2009 -0500 @@ -1,69 +1,65 @@ - - - - - -SDK Support in Carbide.c++ - - - - - -

You're not done installing just yet...

Release: 2.0.3
- Revised: Feb 2009

Read the Release Notes and What's New for the latest infomation about this product. In Carbide.c++ simply click Help > Help Contents > Carbide Help.

To complete your installation and start Symbian C++ application development, you must install the following:

- - - - - - - -

Installing Perl

The Carbide.c++ tools require a copy of Perl to run build scripts:

- Perl (www.activestate.com) -

ActivePerl-5.6.1.635 (5.6.1 is required by Symbian tools, later versions will not work)

- - - - - - - -

Installing SDKs

Also, you must install at least one of the following SDKs to develop Symbian applications: -

NOTE Carbide.c++ requires SDKs built to support WINSCW format.

S60 Platform SDKs (forum.nokia.com/main/resources/tools_and_sdks/carbide/)

S60 5th Edition -
S60 3rd Edition, FP2 -
S60 3rd Edition, FP1 -
S60 3rd Edition, MR -

Qt SDKs (www.trolltech.com)

Qt SDK for S60 -

UIQ SDKs (developer.uiq.com)

UIQ 3.1 -
UIQ 3.0 -

- - - + + + + + +SDK Support in Carbide.c++ + + + + + +

You're not done installing just yet...

Release: 2.1.0
+ Revised: April 2009

Read the Release Notes and Bug Fixes for the latest infomation about this product. In Carbide.c++ simply click the Help > Help Contents > Carbide.c++ User Guide to find the pages.

To complete your installation and start Symbian C++ application development, you must install the following:

+ + + + + + + +

Installing Perl

The Carbide.c++ tools require a copy of Perl to run build scripts:

+ Perl (www.activestate.com) +

ActivePerl-5.6.1.635 (5.6.1 is required by Symbian tools, later versions will not work)

+ + + + + + + +

Installing SDKs

Also, you must install at least one of the following SDKs to develop Symbian applications: +

NOTE Carbide.c++ requires SDKs built to support WINSCW format.

S60 Platform SDKs (forum.nokia.com/main/resources/tools_and_sdks/carbide/)

S60 5th Edition +
S60 3rd Edition, FP2 +
S60 3rd Edition, FP1 +
S60 3rd Edition, MR +

Qt SDKs (www.trolltech.com)

Qt SDK for S60 +

UIQ SDKs (developer.uiq.com)

UIQ 3.1 +
UIQ 3.0 +

+ + + diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp-feature/feature.xml --- a/core/com.nokia.carbide.cpp-feature/feature.xml Mon Apr 06 14:33:24 2009 -0500 +++ b/core/com.nokia.carbide.cpp-feature/feature.xml Mon Apr 06 14:56:28 2009 -0500 @@ -2,7 +2,7 @@ diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/Tools/release_notes.txt diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/book.css --- a/core/com.nokia.carbide.cpp.codescanner/book.css Mon Apr 06 14:33:24 2009 -0500 +++ b/core/com.nokia.carbide.cpp.codescanner/book.css Mon Apr 06 14:56:28 2009 -0500 @@ -1,184 +1,184 @@ -/* - Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies). - All rights reserved. - License: http://www.eclipse.org/legal/epl-v10.html -*/ - -/* Add whitespace around entire display to avoid crowding edges of view */ -/* 20070523-Removed top margin size to close gap between location breadcrumbs and page title */ -html { - margin: 2px 10px 10px 10px; - } - -/* Set default font to serif style, 12-pt and plain */ -body, p, table { - font-family: Georgia, "Times New Roman", Times, serif; - font-size: 13px; - font-weight: normal; -} - -/* Use sans-serif fonts for all title styles */ -h1, h2, h3, h4, h5, h6, strong, em { - font-family: Helvetica, sans-serif; - color: #000000; - } - -h1 { font-size:20px } -h2 { font-size:18px } -h3 { font-size:16px } -h4 { font-size:14px } -h5 { font-size:13px } -h6 { font-size:12px } - -/* For headlines at the top of a view, add space */ -/* 20090224-changed green fade to gold header image */ -h1, h2, h3 { - background-image: url(html/images/brand/gold_header.png); - background-repeat: no-repeat; - padding:10px 0px 10px 12px; - } - -li { - margin-bottom:8px; - margin-top:8px; - } - -/* Footer includes space and a gray line above the company logo */ -#footer { - padding-top:10px; - margin-top:20px; - border-top:1px solid #999; - font-family: Helvetica, sans-serif; - font-size: 11px; - color:#333; - } - -.listing { - font-family: "Courier New", Courier, mono; - color: #000000; - background-color: #FFFFCC; - margin: 5px 0px; - } - -.code, pre { - font-family: "Courier New", Courier, mono; - font-size: 13px; - color: #000000; - } - -.step { - /* background-color: #EEE; */ - /* margin: 10px 0px; */ - color: #111; - /* border-bottom:2px solid #EEE; */ - } - -.substep { - background-color: #EEE; - } - - -/* Figure/Listing/Table titles are centered and gray */ -p.table { - color: #999; - font-weight: bold; - padding-top: 5px; - } - -table { - border: solid #999 1px; - table-layout: auto; - font-size: 13px; - } - -td, th { - border: solid #999 1px; - padding: 5px; - vertical-align:top; - } - -/* 20070522-replaced gray with green background to match gradiant color for title */ -th { - background-color:#FDDD1F; /* background-color:#acd79b; - background-color:#999; - color:#FFF; */ - } - -div.ol.p { - margin-left: 3em; - } - -/* Make all ordered/unordered list items appear in bold gray */ -div ol > li, div ul > li { - font-weight:bold; - color: #333; - } - -div ol > p, div ul > p, div li > p { - font-weight:normal; - } - -/* Make all H4 and H5 items appear in bold gray against a light green background */ -div h5, div h4 { - padding:5px 0px 5px 12px; - background-color:#FFFF66; - /* background-color: #EEE; */ - font-weight:bold; - color: #000000; - } - - -/* Notes stand out using a light top & bottom borders with dark gray text */ -p.note { - /* color: #03C; */ - /* background-color: #FFFF99; */ - color: #333; - padding: 5px; - margin-left: 1em; - margin-right: 1em; - border-top: solid #BBB thin; - border-bottom: solid #BBB thin; - } - - -/* Figure/Listing/Table titles are centered and gray */ -p.figure { - color: #333; - text-align: center; - font-weight: bold; - } - -/* highly visible red background and white text for things that need fixing before release */ -/* SHOULD NOT BE PRESENT IN RELEASED PRODUCTS */ -.fix { - background-color: red; - font-weight: bold; - color: white; - } - -.question { - font-style:italic; - font-weight:bold; - color: #555; - } - -.titleSmall { - font-family: Helvetica, sans-serif; - font-size: 11px; - } - - -.plain { - font-family: Helvetica, sans-serif; - font-size: 12px; - font-style: normal; - line-height: normal; - font-weight: normal; - font-variant: normal; - color: #000000; - text-decoration: none; - } - -a:link { color: #0033CC } -a:visited { color: #555555 } -a:hover { color: #0033CC } +/* + Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies). + All rights reserved. + License: http://www.eclipse.org/legal/epl-v10.html +*/ + +/* Add whitespace around entire display to avoid crowding edges of view */ +/* 20070523-Removed top margin size to close gap between location breadcrumbs and page title */ +html { + margin: 2px 10px 10px 10px; + } + +/* Set default font to serif style, 12-pt and plain */ +body, p, table { + font-family: Georgia, "Times New Roman", Times, serif; + font-size: 13px; + font-weight: normal; +} + +/* Use sans-serif fonts for all title styles */ +h1, h2, h3, h4, h5, h6, strong, em { + font-family: Helvetica, sans-serif; + color: #000000; + } + +h1 { font-size:20px } +h2 { font-size:18px } +h3 { font-size:16px } +h4 { font-size:14px } +h5 { font-size:13px } +h6 { font-size:12px } + +/* For headlines at the top of a view, add space */ +/* 20090224-changed green fade to gold header image */ +h1, h2, h3 { + background-image: url(html/images/brand/gold_header.png); + background-repeat: no-repeat; + padding:10px 0px 10px 12px; + } + +li { + margin-bottom:8px; + margin-top:8px; + } + +/* Footer includes space and a gray line above the company logo */ +#footer { + padding-top:10px; + margin-top:20px; + border-top:1px solid #999; + font-family: Helvetica, sans-serif; + font-size: 11px; + color:#333; + } + +.listing { + font-family: "Courier New", Courier, mono; + color: #000000; + background-color: #FFFFCC; + margin: 5px 0px; + } + +.code, pre { + font-family: "Courier New", Courier, mono; + font-size: 13px; + color: #000000; + } + +.step { + /* background-color: #EEE; */ + /* margin: 10px 0px; */ + color: #111; + /* border-bottom:2px solid #EEE; */ + } + +.substep { + background-color: #EEE; + } + + +/* Figure/Listing/Table titles are centered and gray */ +p.table { + color: #999; + font-weight: bold; + padding-top: 5px; + } + +table { + border: solid #999 1px; + table-layout: auto; + font-size: 13px; + } + +td, th { + border: solid #999 1px; + padding: 5px; + vertical-align:top; + } + +/* 20070522-replaced gray with green background to match gradiant color for title */ +th { + background-color:#FDDD1F; /* background-color:#acd79b; + background-color:#999; + color:#FFF; */ + } + +div.ol.p { + margin-left: 3em; + } + +/* Make all ordered/unordered list items appear in bold gray */ +div ol > li, div ul > li { + font-weight:bold; + color: #333; + } + +div ol > p, div ul > p, div li > p { + font-weight:normal; + } + +/* Make all H4 and H5 items appear in bold gray against a light green background */ +div h5, div h4 { + padding:5px 0px 5px 12px; + background-color:#FFFF66; + /* background-color: #EEE; */ + font-weight:bold; + color: #000000; + } + + +/* Notes stand out using a light top & bottom borders with dark gray text */ +p.note { + /* color: #03C; */ + /* background-color: #FFFF99; */ + color: #333; + padding: 5px; + margin-left: 1em; + margin-right: 1em; + border-top: solid #BBB thin; + border-bottom: solid #BBB thin; + } + + +/* Figure/Listing/Table titles are centered and gray */ +p.figure { + color: #333; + text-align: center; + font-weight: bold; + } + +/* highly visible red background and white text for things that need fixing before release */ +/* SHOULD NOT BE PRESENT IN RELEASED PRODUCTS */ +.fix { + background-color: red; + font-weight: bold; + color: white; + } + +.question { + font-style:italic; + font-weight:bold; + color: #555; + } + +.titleSmall { + font-family: Helvetica, sans-serif; + font-size: 10px; + } + + +.plain { + font-family: Helvetica, sans-serif; + font-size: 12px; + font-style: normal; + line-height: normal; + font-weight: normal; + font-variant: normal; + color: #000000; + text-decoration: none; + } + +a:link { color: #0033CC } +a:visited { color: #555555 } +a:hover { color: #0033CC } diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/html/codescanner.htm --- a/core/com.nokia.carbide.cpp.codescanner/html/codescanner.htm Mon Apr 06 14:33:24 2009 -0500 +++ b/core/com.nokia.carbide.cpp.codescanner/html/codescanner.htm Mon Apr 06 14:56:28 2009 -0500 @@ -1,32 +1,31 @@ - - - - - - CodeScanner User Guide - - - - - -

- - - - - - - - -

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html

CodeScanner User Guide

Version 2.1.1; February, 2009

- + + + + + + CodeScanner User Guide + + + + + +

+ + + + + + + + +

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html

CodeScanner User Guide

Version 2.1.3; April, 2009

+ \ No newline at end of file diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/html/customizing_cs.htm --- a/core/com.nokia.carbide.cpp.codescanner/html/customizing_cs.htm Mon Apr 06 14:33:24 2009 -0500 +++ b/core/com.nokia.carbide.cpp.codescanner/html/customizing_cs.htm Mon Apr 06 14:56:28 2009 -0500 @@ -1,294 +1,299 @@ - -Customizing CodeScanner Rules - - - - -

Customizing CodeScanner Rules

The CodeScanner command line tool currently accepts an XML configuration file, which controls scanning behavior, like the file types to ignore and which rules to apply. Using the elements contained here makes it possible to customize the scanning rules to include new rules unique to your development environment.

This page describes the format of CodeScanner config file (codescannerconfig.xml), which is used for the following purposes:

Controls scanning behavior of the CodeScanner command line tool
Importing/exporting rules and file types from CodeScanner preference pages in Carbide.c++ IDE

CODESCANNERCONFIG.XML File

The CodeScanner config file is an XML formatted file created by CodeScanner when a scan is performed or when the CodeScaner preference settings are exported. The file contains the following elements:

Arguments element – specifies the arguments to be passed to CodeScanner
Sources element – specifies the file types to be ignored by CodeScanner
Scripts element – specifies the rules to be applied by CodeScanner
Severities element – specifies the severity levels of rules to be applied by CodeScanner
Categories element – specifies the categories of rules to be applied by CodeScanner
CustomRules element – specifies user defined rules to be applied by CodeScanner

Arguments Element

Each Arguments element contains one or more of the following arguments:

Input element (<input>, </input>) – Specify an additional directory or file to scan.
Outputformat element (<outputformat>, </outputformat>) – Specify the output format(s) of the results generated by CodeScanner. Currently the following output formats are supported: -
- html – generate HTML report
- xml – generate an XML report
- std – generate messages in standard console output
-
LXR element (<lxr>, </lxr>) – Specify the URL to an LXR site. When this argument is present, CodeScanner generates links to the specified LXR site instead of the local file system.
LXR version element (<lxrversion>, </lxrversion>) – Specify the LXR version when generating links to an LXR site.
Timestampedoutput element (<timestampedoutput>, </timestampedoutput>) – Specify whether to generate results in a time-stamped output directory. Supported values are on and off.

An example of an Arguments element:

<arguments>
-     <input>C:\Symbian\9.2\Epoc32\include</input>
-     <input>C:\CodeScanner_Tests\includes</input>
-     <lxr>http://s60lxr/source/</lxr>
-     - <lxrversion>S60_3_2_200736</lxrversion>
-     <outputformat>html|std</outputformat>
-     <timestampedoutput>on</timestampedoutput>
- </arguments>

Sources Element

Each Sources element can contain one or more Excludes elements.

Excludes element (<excludes>, </excludes>) – Each Excludes element contains a string, which is a regular expression that specifies a file type to be ignored by CodeScanner.

An example of a Sources element:

Scripts Element

Each Scripts element can contain one or more Script elements, each of which corresponds to a CodeScanner script (each script applies a CodeScanner rule):

Script element The name of each Script element matches the name of the corresponding rule, e.g. baseconstruct, forbiddenwords, magicnumbers. Each Script element has the following attributes: -
- enable (boolean) – specifies whether a script is enabled by CodeScanner
- severity (string) – specifies the severity level of a script
- category (string) – specifies the category of a script
In addition, certain script elements also have special child element or attribute: -

wordsRE element (<wordsRE>, </wordsRE>) – Specify the child element of the forbiddenwords script element. The wordsRE element contains a string, which is a regular expression that specifies the forbidden words detected by the forbiddenwords script.
length attribute – Attribute of the longlines script element. The length attribute is a string that specifies the maximum length of a line of code, beyond which the longlines script flags as a problem.
LFunctionIgnoreRE element (<LFunctionIgnoreRE>, </LFunctionIgnoreRE>) – Specify the child element of the LFunctionCantLeave script element. The LFunctionIgnoreRE element contains a string, which is a regular expression that specifies the L-functions to be ignored by the LFunctionCantLeave script when checking for L-functions inside cannot leave.
cclassIgnoreRE element (<cclassIgnoreRE>, </cclassIgnoreRE>) – Specify the child element of the missingcclass script element. The cclassIgnoreRE element contains a string, which is a regular expression that specifies the classes to be ignored by the missingcclass script when checking for C classes not inheriting from other C classes.
openIgnoreRE element (<openIgnoreRE>, </openIgnoreRE>) – Specify the child element of this open script element. The openIgnoreRE element contains a string, which is a regular expression that specifies the classes or objects to be ignored by the open script when checking for ignored return type from Open().
worryRE element (<worryRE>, </ worryRE>) – Child element of the worryingcomments script element. The worryRE element contains a string, which is a regular expression that specifies the worrying comments detected by the worryingcomments script.

Complete list of currently supported Script elements with default attributes:

<scripts>
-
-<accessArrayElementWithoutCheck category="codereview" enable="true" severity="low"/>
-<accessArrayElementWithoutCheck2 category="codereview" enable="true" severity="low"/>
-<activestart category="codereview" enable="true" severity="low"/>
-<activestop category="codereview" enable="true" severity="low"/>
-<arraypassing category="performance" enable="true" severity="medium"/>
-<arrayptrcleanup category="codereview" enable="true" severity="low"/>
-<assertdebuginvariant category="codingstandards" enable="true" severity="low"/>
-
-<baddefines category="codingstandards" enable="true" severity="low"/>
-<baseconstruct category="codereview" enable="true" severity="low"/>
-
-<callActiveObjectWithoutCheckingOrStopping category="codereview" enable="true" severity="low"/> <changenotification category="codereview" enable="true" severity="low"/>
-<cleanup category="codingstandards" enable="true" severity="low"/>
-<commentcode category="codereview" enable="true" severity="low"/>
-<connect category="canpanic" enable="true" severity="high"/>
-<ConnectAndDontCloseMemberVariable category="functionality" enable="true" severity="medium"/> <constnames category="codingstandards" enable="true" severity="low"/>
-<consttdescptr category="codingstandards" enable="true" severity="low"/>
-<controlornull category="canpanic" enable="true" severity="high"/>
-<ctltargettype category="functionality" enable="true" severity="medium"/>
-
-<debugrom category="performance" enable="true" severity="medium"/>
-<declarename category="codingstandards" enable="true" severity="low"/>
-<deleteMemberVariable category="canpanic" enable="true" severity="high"/>
-<destructor category="canpanic" enable="true" severity="high"/>
-<doubleSemiColon category="codereview" enable="true" severity="low"/>
-<driveletters category="codingstandards" enable="true" severity="low"/>
-
-<eikbuttons category="localisation" enable="true" severity="medium"/>
-<eikonenvstatic category="performance" enable="true" severity="medium"/>
-<enummembers category="codingstandards" enable="true" severity="low"/>
-<enumnames category="codingstandards" enable="true" severity="low"/>
-<exportinline category="functionality" enable="true" severity="medium"/>
-<exportpurevirtual category="functionality" enable="true" severity="medium"/>
-
-<foff category="codereview" enable="true" severity="low"/>
-<forbiddenwords category="codingstandards" enable="true" severity="low">
-    <wordsRE>Epoc|Nokia Mobile Phones|NMP|(^|\s)S60</wordsRE>
-</forbiddenwords>
-<forgottoputptroncleanupstack category="codereview" enable="true" severity="low"/>
-<friend category="codereview" enable="true" severity="low"/>
-
-<goto category="codingstandards" enable="true" severity="low"/>
-
-<ifassignments category="codingstandards" enable="true" severity="low"/>
-<ifpreprocessor category="codingstandards" enable="true" severity="low"/>
-<inheritanceorder category="canpanic" enable="true" severity="high"/>
-<intleaves category="codereview" enable="true" severity="low"/>
-
-<jmp category="codingstandards" enable="true" severity="low"/>
-
-<leave category="canpanic" enable="true" severity="high"/>
-<LeaveNoError category="functionality" enable="true" severity="medium"/>
-<leavingoperators category="codereview" enable="true" severity="low"/>
-<LFunctionCantLeave category="codereview" enable="true" severity="low"> <LFunctionIgnoreRE>RunL</LFunctionIgnoreRE> </LFunctionCantLeave>
-<longlines category="codingstandards" enable="true" length="160" severity="low"/>
-
-<magicnumbers category="codingstandards" enable="true" severity="low"/>
-<mclassdestructor category="codingstandards" enable="true" severity="low"/>
-<memberlc category="canpanic" enable="true" severity="high"/>
-<membervariablecallld category="codingstandards" enable="true" severity="low"/>
-<missingcancel category="codingstandards" enable="true" severity="low"/>
-<missingcclass category="canpanic" enable="true" severity="high">     <cclassIgnoreRE>CBase</cclassIgnoreRE>
-</missingcclass>
-<mmpsourcepath category="codingstandards" enable="true" severity="low"/>
-<multilangrsc category="codereview" enable="true" severity="low"/>
-<multipledeclarations category="codingstandards" enable="true" severity="low"/>
-<multipleinheritance category="functionality" enable="true" severity="medium"/>
-<mydocs category="functionality" enable="true" severity="medium"/>
-
-<namespace category="codingstandards" enable="true" severity="low"/>
-<newlreferences category="codingstandards" enable="true" severity="low"/>
-<noleavetrap category="codereview" enable="true" severity="low"/>
-<nonconsthbufc category="codingstandards" enable="true" severity="low"/>
-<nonconsttdesc category="codingstandards" enable="true" severity="low"/>
-<nonleavenew category="codereview" enable="true" severity="low"/>
-<nonunicodeskins category="codereview" enable="true" severity="low"/>
-<null category="codingstandards" enable="true" severity="low"/>
-
-<open category="canpanic" enable="true" severity="high">     <openIgnoreRE>RDesReadStream|RDesWriteStream</openIgnoreRE>
-</open>
-
-<pointertoarrays category="performance" enable="true" severity="medium"/>
-<pragmadisable category="codingstandards" enable="true" severity="low"/>
-<pragmamessage category="codingstandards" enable="true" severity="low"/>
-<pragmaother category="codereview" enable="true" severity="low"/>
-<privateinheritance category="codingstandards" enable="true" severity="low"/>
-<pushaddrvar category="canpanic" enable="true" severity="high"/>
-<pushmember category="canpanic" enable="true" severity="high"/>
-
-<readresource category="canpanic" enable="true" severity="high"/>
-<resourcenotoncleanupstack category="codereview" enable="true" severity="low"/>
-<resourcesonheap category="codingstandards" enable="true" severity="low"/> <returndescriptoroutofscope category="canpanic" enable="true" severity="high"/>
-<rfs category="codereview" enable="true" severity="low"/>
-<rssnames category="codereview" enable="true" severity="low"/>
-
-<stringliterals category="codingstandards" enable="true" severity="low"/>
-<stringsinresourcefiles category="codereview" enable="true" severity="low"/>
-<struct category="codingstandards" enable="true" severity="low"/>
-
-<tcclasses category="functionality" enable="true" severity="medium"/>
-<tclassdestructor category="codingstandards" enable="true" severity="low"/>
-<todocomments category="codereview" enable="true" severity="low"/>
-<trapcleanup category="panic" enable="true" severity="high"/>
-<trapeleave category="performance" enable="true" severity="medium"/>
-<traprunl category="codingstandards" enable="true" severity="low"/>
-<trspassing category="functionality" enable="true" severity="medium"/>
-
-<uids category="codereview" enable="true" severity="low"/>
-<uncompressedaif category="performance" enable="true" severity="medium"/>
-<uncompressedbmp category="performance" enable="true" severity="medium"/>
-<unicodesource category="codereview" enable="true" severity="low"/>
-<userafter category="performance" enable="true" severity="medium"/>
-<userfree category="codereview" enable="true" severity="low"/>
-<userWaitForRequest category="codereview" enable="true" severity="low"/>
-
-<variablenames category="codingstandards" enable="true" severity="low"/>
-<voidparameter category="codingstandards" enable="true" severity="low"/>
-
-<worryingcomments category="codereview" enable="true" severity="low">     <worryRE>\!|\?|[Zz]{3}|kludge|workaround|\scrap|hack</worryRE>
-</worryingcomments>
-
-</scripts>

Severities Element

Each Severities element can contain one or more Severity elements, each of which corresponds to a severity level:

Severity element The name of each Severity element matches the name of the corresponding severity level. Each Severity element has the following attribute: -
- enable (boolean) – Specifies whether scripts of a particular severity level are enabled by CodeScanner.
-

Complete list of currently supported Severity elements:

Categories Element

Each Categories element can contain one or more Category elements, each of which corresponds to a category of CodeScanner scripts:

Category element The name of each Category element matches the name of the corresponding script category. Each Category element has the following attribute: -
- enable (boolean) – Specifies whether scripts of a particular category are enabled by CodeScanner.
-

Complete list of currently supported Category elements:

Customrules Element

Each custom rules element can contain one or more custom rule elements, each of which defines a custom rule to be applied by CodeScanner during scanning operation:

Custom rule element (<customrule>, </customrule>)

Each custom rule element contains the following elements:

Name element (<name>, </name>) – The name element specifies the name used by CodeScanner internally to identify a custom rule. A custom rule element can only have one name element.
Keyword element (<keyword>, </keyword>) – A keyword element specifies a keyword to use when applying a custom rule. A custom rule element can have multiple keyword elements.
-
- A keyword element also has the following attribute: -
- type(string) – specifies the type of a keyword. Here is a list of currently supported keyword types: -
  - baseclass (name of the base class from the declaration of a sub-class)
  - call (name of a called method)
  - class (name used in the declaration/definition of a class)
  - comment (keyword from a comment)
  - generic (keyword used in generic search, i.e. look for anything that matches the keyword)
  - local (name used in the definition of a local variable)
  - macro (name used in the definition of a macro)
  - member (name used in the definition of a data member)
  - method (name used in the declaration/definition of a method)
  - parameter (name of a resource statement parameter)
  -
-
File type element (<filetype>, </filetype>) – A file type element specifies a file extension type to scan when applying a custom rule. A custom rule element can have multiple file type elements. This element is required.
Severity element (<severity>, </severity>) – A severity element specifies the severity level of a custom rule: high, medium or low. A custom rule element can have only one severity element.
Title element (<title>, </title>) – A title element specifies a title message associated with a custom rule. This is used as the title of HTML report or stdout warning/error message generated when applying a custom rule. A custom rule element can have only one title element.
Description element (<description>, </description>) – A description element specifies a detailed description of a custom rule. This is used when generating HTML reports or warning/error messages for stdout when applying a custom rule. A custom rule element can have zero or one description element.
Link element (<link>, </link>) – A link element specifies any external link associated with a custom rule. This is used when generating HTML reports or warning/error messages for stdout when applying a custom rule. A custom rule element can have zero or one link element.

An example of CustomRules element:

<customrules>
-     <customrule>
-         <name>myOwnRule</name>
-         <keyword type=”class”>CMyOwnClass</keyword>
-         <filetype>h</filetype>
-         <severity>low</severity>
-         <title>My own little CodeScanner rule</title>
-         <description>Locate the definition of CMyOwnClass::MyFunction()</description>
-         <link>http://www.myownsite.nokia.com</link>
-     </customrule>
- </customrules>

- - - + +Customizing CodeScanner Rules + + + + +

Customizing CodeScanner Rules

This page describes the format of CodeScanner config file (codescannerconfig.xml), which is used for the following purposes:

Controls scanning behavior of the CodeScanner command line tool
Importing/exporting rules and file types from CodeScanner preference pages in Carbide.c++ IDE

CODESCANNERCONFIG.XML File

The CodeScanner config file is an XML formatted file created by CodeScanner when a scan is performed or when the CodeScaner preference settings are exported. The file contains the following elements:

Arguments element – specifies the arguments to be passed to CodeScanner
Sources element – specifies the file types to be ignored by CodeScanner
Scripts element – specifies the rules to be applied by CodeScanner
Severities element – specifies the severity levels of rules to be applied by CodeScanner
Categories element – specifies the categories of rules to be applied by CodeScanner
CustomRules element – specifies user defined rules to be applied by CodeScanner

Arguments Element

Each Arguments element contains one or more of the following arguments:

Input element (<input>, </input>) – Specify an additional directory or file to scan.
Outputformat element (<outputformat>, </outputformat>) – Specify the output format(s) of the results generated by CodeScanner. Currently the following output formats are supported: +
- html – generate HTML report
- xml – generate an XML report
- std – generate messages in standard console output
+
LXR element (<lxr>, </lxr>) – Specify the URL to an LXR site. When this argument is present, CodeScanner generates links to the specified LXR site instead of the local file system.
LXR version element (<lxrversion>, </lxrversion>) – Specify the LXR version when generating links to an LXR site.
Timestampedoutput element (<timestampedoutput>, </timestampedoutput>) – Specify whether to generate results in a time-stamped output directory. Supported values are on and off.

An example of an Arguments element:

<arguments>
+     <input>C:\Symbian\9.2\Epoc32\include</input>
+     <input>C:\CodeScanner_Tests\includes</input>
+     <lxr>http://s60lxr/source/</lxr>
+     + <lxrversion>S60_3_2_200736</lxrversion>
+     <outputformat>html|std</outputformat>
+     <timestampedoutput>on</timestampedoutput>
+ </arguments>

Sources Element

Each Sources element can contain one or more Excludes elements.

Excludes element (<excludes>, </excludes>) – Each Excludes element contains a string, which is a regular expression that specifies a file type to be ignored by CodeScanner.

An example of a Sources element:

Scripts Element

Each Scripts element can contain one or more Script elements, each of which corresponds to a CodeScanner script (each script applies a CodeScanner rule):

Script element The name of each Script element matches the name of the corresponding rule, e.g. baseconstruct, forbiddenwords, magicnumbers. Each Script element has the following attributes: +
- enable (boolean) – specifies whether a script is enabled by CodeScanner
- severity (string) – specifies the severity level of a script
- category (string) – specifies the category of a script
In addition, certain script elements also have special child element or attribute: +

wordsRE element (<wordsRE>, </wordsRE>) – Specify the child element of the forbiddenwords script element. The wordsRE element contains a string, which is a regular expression that specifies the forbidden words detected by the forbiddenwords script.
length attribute – Attribute of the longlines script element. The length attribute is a string that specifies the maximum length of a line of code, beyond which the longlines script flags as a problem.
LFunctionIgnoreRE element (<LFunctionIgnoreRE>, </LFunctionIgnoreRE>) – Specify the child element of the LFunctionCantLeave script element. The LFunctionIgnoreRE element contains a string, which is a regular expression that specifies the L-functions to be ignored by the LFunctionCantLeave script when checking for L-functions inside cannot leave.
cclassIgnoreRE element (<cclassIgnoreRE>, </cclassIgnoreRE>) – Specify the child element of the missingcclass script element. The cclassIgnoreRE element contains a string, which is a regular expression that specifies the classes to be ignored by the missingcclass script when checking for C classes not inheriting from other C classes.
openIgnoreRE element (<openIgnoreRE>, </openIgnoreRE>) – Specify the child element of this open script element. The openIgnoreRE element contains a string, which is a regular expression that specifies the classes or objects to be ignored by the open script when checking for ignored return type from Open().
worryRE element (<worryRE>, </ worryRE>) – Child element of the worryingcomments script element. The worryRE element contains a string, which is a regular expression that specifies the worrying comments detected by the worryingcomments script.

Complete list of currently supported Script elements with default attributes:

<scripts>
+
+<accessArrayElementWithoutCheck category="codereview" enable="true" severity="low"/>
+<accessArrayElementWithoutCheck2 category="codereview" enable="true" severity="low"/>
+<activestart category="codereview" enable="true" severity="low"/>
+<activestop category="codereview" enable="true" severity="low"/>
+<arraypassing category="performance" enable="true" severity="medium"/>
+<arrayptrcleanup category="codereview" enable="true" severity="low"/>
+<assertdebuginvariant category="codingstandards" enable="true" severity="low"/>
+
+<baddefines category="codingstandards" enable="true" severity="low"/>
+<baseconstruct category="codereview" enable="true" severity="low"/>
+
+<callActiveObjectWithoutCheckingOrStopping category="codereview" enable="true" severity="low"/> <changenotification category="codereview" enable="true" severity="low"/>
+<cleanup category="codingstandards" enable="true" severity="low"/>
+<commentcode category="codereview" enable="true" severity="low"/>
+<connect category="canpanic" enable="true" severity="high"/>
+<ConnectAndDontCloseMemberVariable category="functionality" enable="true" severity="medium"/> <constnames category="codingstandards" enable="true" severity="low"/>
+<consttdescptr category="codingstandards" enable="true" severity="low"/>
+<controlornull category="canpanic" enable="true" severity="high"/>
+<crepository category="other" enable="true" severity="low"/>
+<ctltargettype category="functionality" enable="true" severity="medium"/>
+<customizableicons category="other" enable="true" severity="low">
+     <iconsRE>iconA.bmp|iconB.svg|iconC</iconsRE>
+ </customizableicons>
+
+<debugrom category="performance" enable="true" severity="medium"/>
+<declarename category="codingstandards" enable="true" severity="low"/>
+<deleteMemberVariable category="canpanic" enable="true" severity="high"/>
+<destructor category="canpanic" enable="true" severity="high"/>
+<doubleSemiColon category="codereview" enable="true" severity="low"/>
+<driveletters category="codingstandards" enable="true" severity="low"/>
+
+<eikbuttons category="localisation" enable="true" severity="medium"/>
+<eikonenvstatic category="performance" enable="true" severity="medium"/>
+<enummembers category="codingstandards" enable="true" severity="low"/>
+<enumnames category="codingstandards" enable="true" severity="low"/>
+<exportinline category="functionality" enable="true" severity="medium"/>
+<exportpurevirtual category="functionality" enable="true" severity="medium"/>
+
+<flags category="other" enable="true" severity="low"/>
+<foff category="codereview" enable="true" severity="low"/>
+<forbiddenwords category="codingstandards" enable="true" severity="low">
+    <wordsRE>Epoc|Nokia Mobile Phones|NMP|(^|\s)S60</wordsRE>
+</forbiddenwords>
+<forgottoputptroncleanupstack category="codereview" enable="true" severity="low"/>
+<friend category="codereview" enable="true" severity="low"/>
+
+<goto category="codingstandards" enable="true" severity="low"/>
+
+<ifassignments category="codingstandards" enable="true" severity="low"/>
+<ifpreprocessor category="codingstandards" enable="true" severity="low"/>
+<inheritanceorder category="canpanic" enable="true" severity="high"/>
+<intleaves category="codereview" enable="true" severity="low"/>
+
+<jmp category="codingstandards" enable="true" severity="low"/>
+
+<leave category="canpanic" enable="true" severity="high"/>
+<LeaveNoError category="functionality" enable="true" severity="medium"/>
+<leavingoperators category="codereview" enable="true" severity="low"/>
+<LFunctionCantLeave category="codereview" enable="true" severity="low"> <LFunctionIgnoreRE>RunL</LFunctionIgnoreRE> </LFunctionCantLeave>
+<longlines category="codingstandards" enable="true" length="160" severity="low"/>
+
+<magicnumbers category="codingstandards" enable="true" severity="low"/>
+<mclassdestructor category="codingstandards" enable="true" severity="low"/>
+<memberlc category="canpanic" enable="true" severity="high"/>
+<membervariablecallld category="codingstandards" enable="true" severity="low"/>
+<missingcancel category="codingstandards" enable="true" severity="low"/>
+<missingcclass category="canpanic" enable="true" severity="high">     <cclassIgnoreRE>CBase</cclassIgnoreRE>
+</missingcclass>
+<mmpsourcepath category="codingstandards" enable="true" severity="low"/>
+<multilangrsc category="codereview" enable="true" severity="low"/>
+<multipledeclarations category="codingstandards" enable="true" severity="low"/>
+<multipleinheritance category="functionality" enable="true" severity="medium"/>
+<mydocs category="functionality" enable="true" severity="medium"/>
+
+<namespace category="codingstandards" enable="true" severity="low"/>
+<newlreferences category="codingstandards" enable="true" severity="low"/>
+<noleavetrap category="codereview" enable="true" severity="low"/>
+<nonconsthbufc category="codingstandards" enable="true" severity="low"/>
+<nonconsttdesc category="codingstandards" enable="true" severity="low"/>
+<nonleavenew category="codereview" enable="true" severity="low"/>
+<nonunicodeskins category="codereview" enable="true" severity="low"/>
+<null category="codingstandards" enable="true" severity="low"/>
+
+<open category="canpanic" enable="true" severity="high">     <openIgnoreRE>RDesReadStream|RDesWriteStream</openIgnoreRE>
+</open>
+
+<pointertoarrays category="performance" enable="true" severity="medium"/>
+<pragmadisable category="codingstandards" enable="true" severity="low"/>
+<pragmamessage category="codingstandards" enable="true" severity="low"/>
+<pragmaother category="codereview" enable="true" severity="low"/>
+<privateinheritance category="codingstandards" enable="true" severity="low"/>
+<pushaddrvar category="canpanic" enable="true" severity="high"/>
+<pushmember category="canpanic" enable="true" severity="high"/>
+
+<readresource category="canpanic" enable="true" severity="high"/>
+<resourcenotoncleanupstack category="codereview" enable="true" severity="low"/>
+<resourcesonheap category="codingstandards" enable="true" severity="low"/> <returndescriptoroutofscope category="canpanic" enable="true" severity="high"/>
+<rfs category="codereview" enable="true" severity="low"/>
+<rssnames category="codereview" enable="true" severity="low"/>
+
+<stringliterals category="codingstandards" enable="true" severity="low"/>
+<stringsinresourcefiles category="codereview" enable="true" severity="low"/>
+<struct category="codingstandards" enable="true" severity="low"/>
+
+<tcclasses category="functionality" enable="true" severity="medium"/>
+<tclassdestructor category="codingstandards" enable="true" severity="low"/>
+<todocomments category="codereview" enable="true" severity="low"/>
+<trapcleanup category="panic" enable="true" severity="high"/>
+<trapeleave category="performance" enable="true" severity="medium"/>
+<traprunl category="codingstandards" enable="true" severity="low"/>
+<trspassing category="functionality" enable="true" severity="medium"/>
+
+<uids category="codereview" enable="true" severity="low"/>
+<uncompressedaif category="performance" enable="true" severity="medium"/>
+<uncompressedbmp category="performance" enable="true" severity="medium"/>
+<unicodesource category="codereview" enable="true" severity="low"/>
+<userafter category="performance" enable="true" severity="medium"/>
+<userfree category="codereview" enable="true" severity="low"/>
+<userWaitForRequest category="codereview" enable="true" severity="low"/>
+
+<variablenames category="codingstandards" enable="true" severity="low"/>
+<voidparameter category="codingstandards" enable="true" severity="low"/>
+
+<worryingcomments category="codereview" enable="true" severity="low">     <worryRE>\!|\?|[Zz]{3}|kludge|workaround|\scrap|hack</worryRE>
+</worryingcomments>
+
+ </scripts>

Severities Element

Each Severities element can contain one or more Severity elements, each of which corresponds to a severity level:

Severity element The name of each Severity element matches the name of the corresponding severity level. Each Severity element has the following attribute: +
- enable (boolean) – Specifies whether scripts of a particular severity level are enabled by CodeScanner.
+

Complete list of currently supported Severity elements:

Categories Element

Each Categories element can contain one or more Category elements, each of which corresponds to a category of CodeScanner scripts:

Category element The name of each Category element matches the name of the corresponding script category. Each Category element has the following attribute: +
- enable (boolean) – Specifies whether scripts of a particular category are enabled by CodeScanner.
+

Complete list of currently supported Category elements:

Customrules Element

Each custom rules element can contain one or more custom rule elements, each of which defines a custom rule to be applied by CodeScanner during scanning operation:

Custom rule element (<customrule>, </customrule>)

Each custom rule element contains the following elements:

Name element (<name>, </name>) – The name element specifies the name used by CodeScanner internally to identify a custom rule. A custom rule element can only have one name element.
Keyword element (<keyword>, </keyword>) – A keyword element specifies a keyword to use when applying a custom rule. A custom rule element can have multiple keyword elements.
+
+ A keyword element also has the following attribute: +
- type(string) – specifies the type of a keyword. Here is a list of currently supported keyword types: +
  - baseclass (name of the base class from the declaration of a sub-class)
  - call (name of a called method)
  - class (name used in the declaration/definition of a class)
  - comment (keyword from a comment)
  - generic (keyword used in generic search, i.e. look for anything that matches the keyword)
  - local (name used in the definition of a local variable)
  - macro (name used in the definition of a macro)
  - member (name used in the definition of a data member)
  - method (name used in the declaration/definition of a method)
  - parameter (name of a resource statement parameter)
  +
+
File type element (<filetype>, </filetype>) – A file type element specifies a file extension type to scan when applying a custom rule. A custom rule element can have multiple file type elements. This element is required.
Severity element (<severity>, </severity>) – A severity element specifies the severity level of a custom rule: high, medium or low. A custom rule element can have only one severity element.
Title element (<title>, </title>) – A title element specifies a title message associated with a custom rule. This is used as the title of HTML report or stdout warning/error message generated when applying a custom rule. A custom rule element can have only one title element.
Description element (<description>, </description>) – A description element specifies a detailed description of a custom rule. This is used when generating HTML reports or warning/error messages for stdout when applying a custom rule. A custom rule element can have zero or one description element.
Link element (<link>, </link>) – A link element specifies any external link associated with a custom rule. This is used when generating HTML reports or warning/error messages for stdout when applying a custom rule. A custom rule element can have zero or one link element.

An example of CustomRules element:

<customrules>
+     <customrule>
+         <name>myOwnRule</name>
+         <keyword type=”class”>CMyOwnClass</keyword>
+         <filetype>h</filetype>
+         <severity>low</severity>
+         <title>My own little CodeScanner rule</title>
+         <description>Locate the definition of CMyOwnClass::MyFunction()</description>
+         <link>http://www.myownsite.nokia.com</link>
+     </customrule>
+ </customrules>

+ + + \ No newline at end of file diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/html/images/brand/about_cpp.png Binary file core/com.nokia.carbide.cpp.codescanner/html/images/brand/about_cpp.png has changed diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/html/images/brand/background_carbide.jpg Binary file core/com.nokia.carbide.cpp.codescanner/html/images/brand/background_carbide.jpg has changed diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/html/release_notes.htm --- a/core/com.nokia.carbide.cpp.codescanner/html/release_notes.htm Mon Apr 06 14:33:24 2009 -0500 +++ b/core/com.nokia.carbide.cpp.codescanner/html/release_notes.htm Mon Apr 06 14:56:28 2009 -0500 @@ -1,85 +1,97 @@ - - - - -Release Notes - - - -

Changes from Previous Releases

Added support for Knowledge Base Scanning, the ability to scan code and detect possible API issues related to a specific SDK, for example when porting to a new Touch UI SDK. For each SDK, specific porting information is defined as a set of rules specified in XML files. CodeScanner can merge these into the existing set of CodeScanner rules for scanning operations. The results are displayed in the Console view and as information markers in source code.

2.1.1

Added support for user-defined rules. This can be done by adding a <customrules> element to the configuration file.
When scanning with low severity rules, CodeScanner now generates informative messages instead of warnings when the StdOut output format is selected.
Added support to disable individual error/warning via CodeScanner command embedded in comments.
Added new rule to check whether Cancel() function is called in active object's destructor.
-
Updated active object checking rule to ignore After() from RTimer type member variables.
Updated to skip excluded folders specified in configuration file when generating component summary reports.

2.1.0

Updated to skip excluded folders specified in configuration file when generating component summary reports.
Updated configuration file format to allow passing arguments to CodeScanner. One can now add an <arguments> element to the
- configuration file.
Added new rule to check stack-based resource objects not put on the cleanup stack.
Added new rule to check inheritance order of M and C classes.
-
Updated rule for L-functions that cannot leave. It is now possible to specify functions to be ignored by this rule in the
- configuration file. This is done by adding a <LFunctionIgnoreRE> element to the <LFunctionCantLeave> script element.
-
Updated description of rule for badly-named enum members.
Updated NULL equality check rule to ignore pointer comparisons with NULL inside various __ASSERT_XXX() macros.
Removed duplicate rule for hard-coded external drive letters.
-
Improved rule for accessing array element by [] without checking range.
-

2.0.9

Updated check for Open() to allow assignment of return value on a different line.

2.0.8

Updated check for C class not inheriting from another C class.
Updated check for ignored Open() return value.
Fixed a bug where some scripts cannot be disabled from the configuration file.

2.0.7

Updated standard console output to include severity level and category information in the error/warning messages. -
Incorporated Psyco module to improve scanning performance. Please refer to the document "MIT license.txt" for licensing info.

What's New

Added support to disable individual error/warning messages via CodeScanner command in comments.
Added support to scan code for porting issues related to new SDKs.

Fixed bugs and workarounds

Complete list of CodeScanner bugs fixed

Workarounds for known issues:

none to mention

Technical support

The following support services are available:

Customer feedback - send your comments and suggestions to feedback.carbide@nokia.com

- - - + + + + +Release Notes + + + +

CodeScanner Release Notes v2.1.3

Changes from Previous Releases
What's new
Fixed bugs and workarounds
Technical support

Changes from Previous Releases

Added support for the following IAD user-defined rules. The new rules include: +
- <flags> - new IAD rule to check flag usage
- <crepository> - new IAD rule to check Central Repository usage
- <customizableicons> - new IAD rule to check customizable icons
+

2.1.2

Added support for Knowledge Base Scanning, the ability to scan code and detect possible API issues related to a specific SDK, for example when porting to a new Touch UI SDK. For each SDK, specific porting information is defined as a set of rules specified in XML files. CodeScanner can merge these into the existing set of CodeScanner rules for scanning operations. The results are displayed in the Console view and as information markers in source code.

2.1.1

Added support for user-defined rules. This can be done by adding a <customrules> element to the configuration file.
When scanning with low severity rules, CodeScanner now generates informative messages instead of warnings when the StdOut output format is selected.
Added support to disable individual error/warning via CodeScanner command embedded in comments.
Added new rule to check whether Cancel() function is called in active object's destructor.
+
Updated active object checking rule to ignore After() from RTimer type member variables.
Updated to skip excluded folders specified in configuration file when generating component summary reports.

2.1.0

Updated to skip excluded folders specified in configuration file when generating component summary reports.
Updated configuration file format to allow passing arguments to CodeScanner. One can now add an <arguments> element to the
+ configuration file.
Added new rule to check stack-based resource objects not put on the cleanup stack.
Added new rule to check inheritance order of M and C classes.
+
Updated rule for L-functions that cannot leave. It is now possible to specify functions to be ignored by this rule in the
+ configuration file. This is done by adding a <LFunctionIgnoreRE> element to the <LFunctionCantLeave> script element.
+
Updated description of rule for badly-named enum members.
Updated NULL equality check rule to ignore pointer comparisons with NULL inside various __ASSERT_XXX() macros.
Removed duplicate rule for hard-coded external drive letters.
+
Improved rule for accessing array element by [] without checking range.
+

2.0.9

Updated check for Open() to allow assignment of return value on a different line.

2.0.8

Updated check for C class not inheriting from another C class.
Updated check for ignored Open() return value.
Fixed a bug where some scripts cannot be disabled from the configuration file.

2.0.7

Updated standard console output to include severity level and category information in the error/warning messages. +
Incorporated Psyco module to improve scanning performance. Please refer to the document "MIT license.txt" for licensing info.

What's New

Added support to disable individual error/warning messages via CodeScanner command in comments.
Added support to scan code for porting issues related to new SDKs.

Fixed bugs and workarounds

Complete list of CodeScanner bugs fixed

Workarounds for known issues:

none to mention

Technical support

The following support services are available:

Customer feedback - send your comments and suggestions to feedback.carbide@nokia.com

+ + + diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/schema/CSConfig.ecore diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.codescanner/schema/CSConfig.genmodel diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Mon Apr 06 14:33:24 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Mon Apr 06 14:56:28 2009 -0500 @@ -17,9 +17,14 @@

This is a comprehensive list of bugs fixed by release:

Bugs Fixed in v2.1.0

Bugs Fixed in v2.0.4

8050 - Fixed an issue that preventing the building of a target when another target of the same project is being debugged.

Carbide.c++ Release Notes 2.0.4

Carbide.c++ Release Notes 2.1.0

The Carbide.c++ is a comprehensive development tool suite for Symbian OS that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE.

This is a collection of important information concerning last-minute changes and other topics that deserve special attention. Please @@ -35,10 +35,14 @@ Updating the CDT feature in Carbide.c++/Eclipse will wipe out our changes making the tools unusable!

See the Tips & tricks page for more helpful information.

What's New in 2.0.4

What's New in 2.1.0

The following features for Symbian OS development are provided within Carbide.c++:

Hover Help - pause the pointer over a resolved Symbian symbol in the C/C++ editor to view information from the Symbian API Reference for quick reference.
??? -

2.0.4

Hover Help - hover your pointer over a recognized Symbian symbol in an editor and see the Symbian API Reference information appear to assist you.

2.0.3

Welcome to Carbide.c++ 2.0.4

Thank you for installing Carbide.c++2.0! It's an improvement over 1.3.1 with many improvements to connecting and debugging on devices, faster downloading of large SIS files, improved program counter control, C/C++ indexer improvements, and is based on the latest Eclipse and CDT updates (Ganymede).

Welcome to Carbide.c++ 2.1.0

Thank you for installing Carbide.c++2.1! It's an improvement over 2.0 with many improvements including editor hover help and numerous bug fixes.

However, perhaps the best part about Carbide.c++ is the Carbide.c++ Plug-in SDK that you can use to build custom extensions for Carbide.c++. Take a look, and let us know what you built!

Finally, if you find bugs, please let us know by submitting it at the new Carbide Bugzilla bug tracking site located at https://xdabug001.ext.nokia.com/bugzilla

For any other questions, please don't hesitate to contact us.

+ value="Version 2.1.0"/> @@ -40,7 +40,7 @@ + value="Carbide.c++ v2.1.0 for Symbian"/> diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp/splash.bmp Binary file core/com.nokia.carbide.cpp/splash.bmp has changed diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp/themes/carbide/graphics/contentpage/background.jpg Binary file core/com.nokia.carbide.cpp/themes/carbide/graphics/contentpage/background.jpg has changed diff -r 8254273d11c0 -r 887bd61e1328 core/com.nokia.carbide.cpp/themes/carbide/graphics/root/background.jpg Binary file core/com.nokia.carbide.cpp/themes/carbide/graphics/root/background.jpg has changed