https://sourceforge.net/p/cppchecker/feature-requests/2013-01-02T15:22:29ZRecent changes to feature-requests2013-01-02T15:22:29Z2013-01-02T15:22:29ZRalf Hainhttps://sourceforge.net/u/ralfhain/https://sourceforge.net5f2e6f9ff808260b97b07e60bf6063e8671f8368

<div class="markdown_content"><p>The plugin does too much for me. 1) invokes PC-Lint with options 2) analyzes the output. <br /> I’d be glad, if it could do step 1 by myself and let the plugin just do 2. <br /> Background:<br /> In my project the options are generated for each file separately by an elaborate makefile. This cannot be handled by the plugin.<br /> I’ve tried to fill the plugins “Lint call”-field with “cat XYZ.lint”, but this does not work. ("make XYZ.lint &amp;&amp; cat XYZ.lint" also not)<br /> Of cause its clear to me, that I have to provide the right –format option to PC-Lint.</p></div>

2010-07-07T12:14:40Z2010-07-07T12:14:40ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net9545decb713cc5f0a53a0b829801d0756b658e04

<div class="markdown_content"><p>I'm using this with PC-Lint with excellent results. Keep up the good work!</p> <p>One requirement of our processes is that we record code reviews, verification, validation, etc. so that we have evidence that we complied with the processes. PC-Lint can obviously generate a log file (e.g. redirect console to a file), but CppChecker grabs the output itself. Is there a method of capturing the console output to a file within CppChecker?</p> <p>On the same subject, the console output of PC-Lint doesn't appear in the Eclipse CppChecker Console pane. That in itself would be useful for debugging some of the more obscure configuration errors. I'm using Eclipse Version: 3.5.2 and CppChecker 0.9.9.5</p></div>

2010-03-24T10:19:03Z2010-03-24T10:19:03ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net5de6284dfbb6906f488cc74df54a3f1aacf45f16

<div class="markdown_content"><p>I am using the latest PCLint version, v8.0x and just tried the CppChecker plugin. I get the following warning messages and the CppChecker PCLint parser doesnt seem to work.</p> <p>Description Resource Path Location Type<br /> error starting lint, got: PC-lint for C/C++ (NT) Vers. 8.00x, Copyright Gimpel Software 1985-2008<br /> expected: .*Vers. 8.00u.*... myProject myProjectPath CppChecker Common Problem</p> <p>Can I change this somewhere myself, or please update your plugin. Would be awesome!</p> <p>Thanx in advance.</p></div>

2009-08-31T07:06:41Z2009-08-31T07:06:41ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net45a4f60b47a856dccca0e58ea36ccaa17f5c3b84

<div class="markdown_content"><p>I would like to know when the support for splint is planned. This feature would be very interesting feature for me.</p></div>

2008-06-24T20:56:46Z2008-06-24T20:56:46ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.nete1403808cdb148b57a5a1d7973aabdd1c06cf9d7

<div class="markdown_content"><p>Hi,<br /> Thanks for this great plugin.<br /> Might it be possible to expand environment variable<br /> e.g. ${myvar1} as defined in the preference or project settings of eclipse for Pc-Lint settings ?</p> <p>rgds,<br /> Karl</p></div>