To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

How to make fewer errors at the stage o…

How to make fewer errors at the stage of code writing. Part N2

Mar 29 2011

This is the second article on avoiding certain errors at the early stage of code writing. In the previous post, we have already advised you to avoid a large number of calculations in one expression. However, we should investigate this question in detail. Let's see what's dangerous about complex expressions and how we can avoid many logical errors.



You may read the previous post here. This time we'll take error samples from various famous projects to stress their prevalence. The errors I'm going to demonstrate here were found with the help of the PVS-Studio analyzer during a relatively large term. I have informed developers of almost all the projects about the errors, so I hope they will fix the defects in new code revisions. I'm writing this in introduction because I always receive letters after publishing articles with a request "please inform the project's developers about the errors you've found".

1. Do not use the ternary operation '?:' in compound expressions

A ternary conditional operation is written in C/C++ code with the '?:' operator. This is an operation that returns its second or third operand depending on the value of the logical expression defined by the first operand. For example:

int minValue = A < B ? A : B;

A ternary operation has a very low priority (see the table). Programmers often forget about it and that is why the ternary operation is quite dangerous.


Figure 1 - C/C++ operations arranged in priority descending order

Note that the '?:' operation has a lower priority than addition, multiplication, bitwise OR operator and so on. Consider this code:

int Z = X + (A == B) ? 1 : 2;

It works differently than it might seem at first sight. Most likely, the programmer intended to add the X value to number 1 or 2 depending on the (A == B) condition. But actually it is the "X + (A == B)" expression which is the condition. In fact, it is this code written in the project:

int Z = (X + (A == B)) ? 1 : 2;

While the programmer wanted this to be:

int Z = X + (A == B ? 1 : 2);

What occurs to you first is that you just should know the priorities of operations. Well, programmers do know them but too insidious is this ternary operation! Not only novices make mistakes with it but experienced programmers as well. You may easily find them even in the most quality code. Here are a couple of examples.


V502 Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '*' operator. physics dgminkowskiconv.cpp 1061

dgInt32 CalculateConvexShapeIntersection (...)
  den = dgFloat32 (1.0e-24f) *
        (den > dgFloat32 (0.0f)) ? 
           dgFloat32 (1.0f) : dgFloat32 (-1.0f);

V502 Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '-' operator. views 400

static const int kClientEdgeThickness;
int height() const;
bool ShouldShowClientEdge() const;
void CustomFrameView::PaintMaximizedFrameBorder(gfx::Canvas* canvas) {
  int edge_height = titlebar_bottom->height() -
                    ShouldShowClientEdge() ? kClientEdgeThickness : 0;

V502 Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '|' operator. vm vm_file_win.c 393

#define FILE_ATTRIBUTE_NORMAL    0x00000080
#define FILE_FLAG_NO_BUFFERING    0x20000000
vm_file* vm_file_fopen(...)
           (islog == 0) ? 0 : FILE_FLAG_NO_BUFFERING;

As you may see, errors of this type deserve consideration. That is why I've made a separate paragraph to describe them. They are quite widely-spread. I could give you some more examples but they all are similar.

You can avoid such errors if you give up trying to place several operations into a single line of code. Or if you still want to do that, do not be greedy to add parentheses. I will speak of parentheses a bit later. Now let's try to avoid potential errors when using '?:'.

Of course the '?:' operator is certainly a syntactic sugar and you can replace it with if in most cases. Among rare exceptions are such tasks as reference initialization:

MyObject &ref = X ? A : B;

Certainly there are no problems with it either, but creation of a reference to A or B without '?:' operator takes more lines of code to implement:

MyObject *tmpPtr;
If (X)
  tmpPtr = &A;
  tmpPtr = &B;
MyObject &ref = *tmpPtr;

So, we should not refuse to use the '?:' operator. But you might easily make a mistake using it. So I have made up a rule for myself: the '?:' operator's result must be immediately stored somewhere and it should not be combined together with any other actions. That is, there must be an assignment operation to the left of the '?:' operator's condition. Let's return to the original sample:

int Z = X + (A == B) ? 1 : 2;

I suggest that this code should be written this way:

int Z = X;
Z += A == B ? 1 : 2;

In case of an IPP Samples code sample, I would write it so:

mds[3] |= (islog == 0) ? 0 : FILE_FLAG_NO_BUFFERING;

You may disagree with this recommendation and I will not defend it. For instance, I myself do not like having two lines or more instead of one line. Another nice alternative is the obligatory enclosure of the '?:' operator inside parentheses. The main task for me is to show you error patterns, but it depends on programmer's preference what pattern of error protection to choose.

2. Do not feel shy to use parentheses

It has become a custom for some reason that using additional parentheses in C/C++ programming is considered something shameful. Perhaps it is because the question about operations' priorities is often asked at interview and people subconsciously start trying to use the priority mechanism to the full extent all the time - if he makes additional parentheses, they will think he's a novice and not a true Jedi.

I even came across a discussion on the Internet where some man was too dogmatic saying that using additional parentheses is a bad form and that if somebody is not sure about the way an expression will be calculated, he must study instead of writing programs. Unfortunately, I've failed to find this discussion but I do not agree with such opinions. Of course, you must know priorities but if you use heterogeneous operations in an expression, you'd better use parentheses to secure yourself from errors. This will not only protect you from potential errors but make code readable for other developers.

Not only novice programmers but also skillful ones make mistakes caused by confusion of priorities. An expression does not necessarily need to be quite complicated and long; you may make a mistake in relatively simple expressions. Let's consider some examples.


V564 The '&' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '&&' operator. game g_client.c 1534

#define SVF_CASTAI 0x00000010
char *ClientConnect(...) {
  if ( !ent->r.svFlags & SVF_CASTAI ) {

V564 The '&' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '&&' operator. dosbox sdlmain.cpp 519

static SDL_Surface * GFX_SetupSurfaceScaled(Bit32u sdl_flags, 
                                            Bit32u bpp) {
  if (!sdl.blit.surface || (!sdl.blit.surface->flags&SDL_HWSURFACE)) {

And one more sample from Chromium:

V564 The '&' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '&&' operator. base 216

bool GetPlatformFileInfo(PlatformFile file, PlatformFileInfo* info) {
  info->is_directory =
    file_info.dwFileAttributes & FILE_ATTRIBUTE_DIRECTORY != 0;

The expressions are simple. The developers are attaboys. Still there are errors. So, using parentheses in slippery fragments will not be superfluous.

I think the following is the best way: when operations are simple and usual, you don't need additional parentheses. For example:

if (A == B && X != Y)
if (A - B < Foo() * 2)

But if you use rarer operators (~, ^, &, |, <<, >>, ?:), you'd better add explicit parentheses. They will both make code clearer and secure you from a potential error. For example:

If ( ! (A & B))
x = A | B | (z < 1 ? 2 : 3);

Exploiting parentheses when using rare operations will also help you with the "?:" operator discussed above. How we should handle "?:" is a matter of taste. Personally I like the method of simplification.


Write simple and clear code. Splitting long and complex expressions into several strings you get longer code. But this code is much clearer to read and comprehend. It is less probable that you will make a mistake in such code. Do not be afraid to create an additional variable - the compiler will optimize the code well.

Do not be greedy about using parentheses in expressions where rare operators are used or where bit and logical operations are mixed.

A programmer who will read your code with brackets in future will only be grateful to you for it.

Popular related articles
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →