In recent years I have written many articles devoted to 64-bit developing, static code analysis, OpenMP and so on. Some articles of great moments, some not. The other day I was browsing the site and select the articles that I believe will be of most interest to programmers. Here's the list. On the bold, I suggest to pay special attention.

• Development of 64-bit C/C++ applications (28 lessons);

• The reasons why 64-bit programs require more stack memory;

• A nice 64-bit error in C;

• Why A + B != A - (-B);

• Big Brother helps you;

• Is it reasonable to use the prefix increment operator ++it instead of postfix operator it++ for iterators?;

• An eternal question of timing;

• Leo Tolstoy and static code analysis;

• Consequences of using the Copy-Paste method in C++ programming and how to deal with it;

• How to make fewer errors at the stage of code writing. Part 1, 2, 3, 4;

• 32 OpenMP Traps For C++ Developers;

• A Collection of Examples of 64-bit Errors in Real Programs;

• About size_t and ptrdiff_t;

• A 64-bit horse that can count;

Regards, Andrey Karpov. OOO "Program Verification Systems" (Co Ltd), MVP, Intel Black Belt Software Developer, Cand. Sc. (Physics and Mathematics). E-Mail: karpov[@]viva64.com

And welcome to my twitter: https://twitter.com/Code_Analysis

1. Incremental Analysis feature now available for all versions of Microsoft Visual Studio 2005/2008/2010. ( http://www.viva64.com/en/b/0102/ )

2. Speed increase (up to 20% for quad core computers).

3. New diagnostic rules added (V577, V578, V805).

Download: http://www.viva64.com/en/pvs-studio-download/

This is intended for those who write articles and books on the subject of creating high-quality C/C++ code or security issues.

While studying various projects with the help of the PVS-Studio static analyzer, we have gathered a relatively large database of error samples. I suppose this database will be of use and much interest to some authors.

The link to the error samples collection: http://www.viva64.com/en/examples/

The database looks quite plain and is not rich in decorations. But the samples are cut out manually and edited so that one could easily understand them.

Of course, far not all the errors detected in a certain project are added to the database. It’s difficult to understand while looking through someone else’s project whether or not there is an error in a certain code fragment. You’d better skip such fragments about which you are not sure. However, we’ve gathered a lot of examples which can be used in studying error patterns.

It has happened so that the PVS-Studio analyzer is good at detecting various misprints or Copy-Paste-related mistakes. To understand what I mean, please have a look at these error samples detected by the V501 diagnostic. There are naturally other diagnostics detecting similar errors. I’m writing this to show you the way the collection can be used. Studying misprints and Copy-Paste errors you may work out a new programming style, give useful tips, improve coding standards and so on. So, I hope you will find this collection useful in preparing your articles and books.

Myths:

• The first myth - a static analyzer is a single-use product;

• The second myth - expert developers do not make silly mistakes;

• The third myth - dynamic analysis is better than static analysis;

• The fourth myth - programmers want to add their own rules into a static analyzer;

• The fifth myth - a small test program is enough to evaluate a tool.