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
lordylike
Daniel Marjamäki
rikardfalkeborn
Paul Fultz II
umanamente