b839ad60dd
Fix issue 6856: add checks in isOppositeCond when using == and < or > ( #1298 )
...
* Fix issue 6856: add checks in isOppositeCond when using == and < or >
* Move tests to testcondition
* Fix some more tests
* Fix test messages
* Remove the float check
2018-08-05 22:39:40 +02:00
ddbe4b89b5
Renamed --debug to --debug-simplified
2018-08-05 11:19:20 +02:00
bcdd58de0b
astyle formatting
...
[ci skip]
2018-08-05 10:48:28 +02:00
0e491b41a8
Clarify warning message for 'Same expression on both sides of operator'
2018-08-05 10:48:02 +02:00
ed197f235a
Fix issue 4693: Diagnostic when using the same iterators to an algorithm ( #1326 )
...
* Fix issue 4693: Diagnostic when using the same iterators to an algorithm
* Update classinfo
2018-08-05 09:10:54 +02:00
710d7ce015
Add checks of log2 and log1p range ( #1324 )
...
* Add tests for log10{,f,l} valid arguments
* Add log2{,f,l} to checkfunctions
* Add log1p{,f,l} to checkfunctions
* checkfunctions: Simplify check for log function limit out of range
The conditions for negative and non-negative int and float were
identical so the call to isNegative can be removed and the if-statements
be simplified.
2018-08-03 12:14:39 +02:00
0a66f5c4f9
astyle formatting
...
[ci skip]
2018-07-26 22:24:00 +02:00
e2a4b1706c
Refactoring CheckStl::mismatchingContainers; Use AST
2018-07-26 22:23:37 +02:00
86721f5b91
small refactorings
2018-07-26 22:08:05 +02:00
d471c27502
astyle formatting
...
[ci skip]
2018-07-26 22:03:49 +02:00
0d35a96594
Improve checking of mismatch iterators ( #1293 )
2018-07-26 22:00:48 +02:00
54e2726bf3
Fixed #8636 (Misleading verbose message if virtual method called from destructor)
2018-07-26 09:16:17 +02:00
c666f74755
astyle formatting
...
[ci skip]
2018-07-25 23:02:16 +02:00
f093692551
ValueFlow: Set values in else branch even when the first branch modifies the value ( #1309 )
...
* Set values in else branch even when the first branch modifies the value
* Move tests
* Add check for goto
* Remvoe todo
* Also check scope is noreturn
* Use isEscapeScope when variables are changed
2018-07-25 22:59:54 +02:00
01ceb9bae7
fixed issue 8661: Misleading error message when compilation database is not recognized
2018-07-25 16:26:25 +02:00
58c91c4645
Revert "Refactoring endsWith utility function"
...
This reverts commit d300d1f61b
2018-07-25 16:14:43 +02:00
f9a5a114bb
astyle formatting
...
[ci skip]
2018-07-25 07:44:06 +02:00
d300d1f61b
Refactoring endsWith utility function
2018-07-25 07:43:50 +02:00
9895ea5ff2
Fix issue 470: Condition is always true or false on logical operators ( #1294 )
...
* Fix issue 470: Condition is always true or false on logical operators
* Dont warn on literals
* Compute logical operators using valueflow
* Fix FP when using literals
* Always warn on subconditions that are always true
* Use percent matches first
* Add test for logical operators
* Check if parent is null
2018-07-23 08:51:59 +02:00
12e58c8521
fix ticket 8570: passedByValue with member initializer list and std::move ( #1316 )
...
* fix ticket 8570
allow member initializer list variables that are moved to be non-const
* review feedback
* replace tabs with spaces in test code
2018-07-22 15:01:18 +02:00
77b653bf94
Clarify warnings when char literals are converted to bool in conditions
2018-07-21 18:40:06 +02:00
417670d947
Clarify code with continue
2018-07-20 21:44:23 +02:00
30a8d953e3
Move sqrt{,f,l} argument checks to cfg file ( #1313 )
2018-07-20 20:56:39 +02:00
7c4820e047
Rename Library::isargvalid()
2018-07-15 23:05:48 +02:00
491ee577c6
Support floats in valid config ( #1297 )
...
* Add tests for invalid ranges
* Refactor loadLibErrors
This reduces the amount of code slightly and will simplify adding
more tests.
* Handle empty valid field
Before this change, the sequence <valid></valid> in a config file would
result in a segmentation fault. Now an empty field results in the error
message:
cppcheck: Failed to load library configuration file 'mycfg.cfg'. Bad attribute value '""'
* Add support for valid for floating point arguments
Previously, it was not possible to add valid ranges to floating point
arguments since it only handled integers. This made ranges not work well
for floating point arguments since arguments were cast to integers
before the ranges were handled.
Fix this by using doubles instead of integers if the argument is a float.
Add some tests for this and make sure errors are printed with enough
precision (somewhat arbitrarily chosen).
Note that it is still only possible to add integer ranges (i.e. -1:1).
* Add support for floats in configuration valid range
Now that it is possible to handle decimal arguments, there is no reason
to not allow non-integer ranges. Take care to not allow broken
configurations.
* Move check to within if-clause
* Move asin{,f,l} and acos{,f,l} input checks to config file
2018-07-15 22:47:56 +02:00
39857220ce
Refactoring: Use range for loops
2018-07-15 15:08:35 +02:00
cc5f00c252
Refactoring; use range for loops
2018-07-15 15:03:08 +02:00
518dd8bfa3
Refactoring: Use range for loops
2018-07-15 14:51:33 +02:00
1c4fb47582
astyle formatting
...
[ci skip]
2018-07-15 14:45:33 +02:00
faea8e1c02
Refactoring: Use range for loops
2018-07-15 14:45:15 +02:00
5d1fdf7958
Fix issue 7904: Handle double nots in isSameExpression ( #1305 )
...
* Fix issue 7904: Handle double nots in isSameExpression
* Skip checking double nots in assignments
* Use ast to check for double not
2018-07-15 11:30:02 +02:00
60485df762
Refactoring; Use range for loops
2018-07-14 22:49:31 +02:00
991300ac54
Clarify code with Token::isUnaryOp()
2018-07-14 22:36:08 +02:00
1e824330c0
Refactoring: Use range for loops
2018-07-14 22:26:22 +02:00
0f3cc56c59
Refactoring: Use range for loops
2018-07-14 13:19:41 +02:00
d603a811bb
Clarify code with Token::hasKnownValue()
2018-07-14 13:09:53 +02:00
d00e522856
Clarify the code with Token::isUnaryOp and Token::isBinaryOp
2018-07-14 13:01:24 +02:00
c9a2071420
Refactoring: Use range for loop
2018-07-14 12:28:57 +02:00
0c84475aac
Clarify code with Token::isUnaryOp()
2018-07-14 10:26:22 +02:00
449c48f6a7
Refactoring: Use range for loops
2018-07-14 10:23:41 +02:00
c7b787888a
Refactoring: Use range for loops
2018-07-14 10:09:12 +02:00
7dda8e2a2d
Refactoring: Use range for loops
2018-07-14 10:02:32 +02:00
eeda082a2f
Refactoring: use range for loops
2018-07-14 09:54:52 +02:00
bb36adb432
Refactoring; Use range for loops
2018-07-14 09:49:03 +02:00
c60763bc14
Refactoring; Use range for loop
2018-07-14 08:18:10 +02:00
5b1d96b346
Clarify code with Token::isUnaryOp()
2018-07-14 08:04:08 +02:00
4429ee55c3
Refactoring; Use range for loop
2018-07-14 07:55:18 +02:00
1dd647ae84
Refactoring; Use range for loop
2018-07-14 07:49:04 +02:00
d759015d99
Refactoring; Use range for loops
2018-07-13 23:51:22 +02:00
594e07acaa
Refactoring; Use range for loop
2018-07-13 23:45:34 +02:00
58ac8a9982
Refactoring; Use range for loops
2018-07-13 23:43:03 +02:00
ed76f06ca7
Refactoring; use range for loop
2018-07-13 23:32:49 +02:00
b2403c36cd
Refactoring; Use Token::isUnaryOp() to clarify code
2018-07-13 23:17:24 +02:00
54cfdb731e
Refactoring; Use Token::isUnaryOp() to clarify code
2018-07-13 23:12:20 +02:00
2c90a83695
Refactoring; Use Token::isBinaryOp() to clarify code, use early continue in loop
2018-07-13 23:06:45 +02:00
a4fdef8d9e
Refactoring; Use Token::isUnaryOp() to clarify code
2018-07-13 23:02:52 +02:00
5712366a8f
refactoring; use range for loops
2018-07-13 22:56:20 +02:00
93903d96c4
Refactoring, use Token::isUnaryOp and Token::isBinaryOp
2018-07-13 18:52:03 +02:00
435888f82e
Refactoring; use range for loop
2018-07-13 16:57:17 +02:00
4d52949be6
Refactoring: Use ranged for loop
2018-07-13 16:50:12 +02:00
e552737028
Refactoring: Use range for loop
2018-07-13 16:46:29 +02:00
2c49732eb8
Added Token::isUnaryOp()
2018-07-13 16:40:32 +02:00
2963522d5f
Refactoring: Use ranged for loops
2018-07-13 16:40:15 +02:00
2b125e013a
Code refactoring, no functional change intended
2018-07-13 09:20:53 +02:00
42f075c3fa
Skip literals for always true/false ( #1304 )
2018-07-12 23:06:47 +02:00
b398398dec
Fixed #8360 (false positive "Ineffective call of function 'empty()'")
2018-07-10 22:58:02 +02:00
44416862c0
Fixed Visual Studio Natvis file after recent refactoring ( #1299 )
2018-07-09 08:27:26 +02:00
03faa25d12
Conditions: Better handling of function calls
2018-07-08 15:58:04 +02:00
24dd4c9c26
Restore code in checkVariableScope. Fixes false negative
2018-07-01 22:31:45 +02:00
4c6270f9b2
Refactoring: use range for loop
2018-06-30 15:34:48 +02:00
60ac463a79
CheckClass: Restore a few warnings about member initialization of classes
2018-06-29 22:54:12 +02:00
61c56eda44
Tweak the CheckClass::constructors() check
2018-06-27 14:02:57 +02:00
79664abf2a
Refactoring: Use range for loop
2018-06-27 09:14:03 +02:00
10e693a8c3
Revert "SymbolDatabase: Improved lookup of function calls"
...
This reverts commit 3c87d60d5d
2018-06-26 23:14:12 +02:00
3c87d60d5d
SymbolDatabase: Improved lookup of function calls
2018-06-26 22:12:12 +02:00
c583fb9186
Revert "SymbolDatabase: Improved lookup of function calls"
...
This reverts commit e4a70f87e6
2018-06-26 13:05:33 +02:00
e4a70f87e6
SymbolDatabase: Improved lookup of function calls
2018-06-26 11:38:45 +02:00
009287f912
Set version to 1.84.99/1.85 dev
2018-06-25 21:03:43 +02:00
3155f15325
CheckClass: Use Variable::valueType()
2018-06-24 16:14:11 +02:00
9fab15bb53
CheckClass: Use Variable::valueType() instead of Variable::typeStartToken
2018-06-24 15:41:16 +02:00
cb48aae594
buffer overrun: Remove bailout. There is no test case and I fail to produce false positives.
2018-06-24 09:50:55 +02:00
d0819e4792
Reuse isVariableChanged() in auto variables
2018-06-24 08:55:23 +02:00
cde63c7573
Use Variable::valueType instead of Variable::typeStartToken in auto variables
2018-06-24 08:25:19 +02:00
2beeca3ca2
Refactoring; use early continue
2018-06-23 23:26:37 +02:00
655a8b21b6
Fix false positive 'passedByValue' when address of argument is used
2018-06-23 23:25:06 +02:00
697aee143f
CheckOther: Use Variable::valueType() instead of Variable::typeStartToken
2018-06-23 16:52:40 +02:00
fc78530b3f
CheckOther: Use Variable::valueType() instead of Variable::typeStartToken
2018-06-23 16:49:26 +02:00
2a8296879c
CheckOther: Use Variable::valueType() instead of Variable::typeStartToken
2018-06-23 16:42:36 +02:00
ee335e5151
Fix compiler error
2018-06-23 16:07:02 +02:00
911020f601
Refactoring, use range for loop
2018-06-23 15:58:44 +02:00
d811a07aa3
CheckOther: Use Variable::valueType() instead of typeStartToken etc
2018-06-22 23:04:36 +02:00
d0614b9b36
varScope: Fix false negatives for references
2018-06-22 22:51:03 +02:00
d90c38802f
Fixed Cppcheck warnings (variable scope can be reduced)
2018-06-21 06:54:56 +02:00
439d4a4900
Use Variable::valueType() instead of Variable::typeStartToken()
2018-06-20 19:08:09 +02:00
10fc070f44
SymbolDatabase: Better handling of type aliases in ValueType
2018-06-20 14:49:55 +02:00
b62c562a89
Try to make Travis happy
2018-06-20 14:13:04 +02:00
0b65a52224
Add some missing errors to --errorlist output. ( #1292 )
...
Partly fixes https://trac.cppcheck.net/ticket/7772 .
2018-06-20 10:43:13 +02:00
929725f3aa
Code cleanup
2018-06-20 10:39:21 +02:00
b4cb2505c3
SymbolDatabase: Add Variable::valueType(). First step to reuse ValueType handling in Variable
2018-06-20 10:00:15 +02:00
eb978ee192
Refactoring: delete assignment operator
2018-06-19 14:00:50 +02:00
Paul Fultz II
Daniel Marjamäki
rikardfalkeborn
firewave
lordylike
umanamente
PKEuS
Sebastian