Group items tagged

m addressing developers with a specific request. Our plans for the PVS-Studio 5.00 static code analyzer are to implement integration with the C++Builder environment and support for the C++/CX language extension. Unfortunately, we have very few projects developed in that environment or involving that extension, and we find it therefore difficult to test the new functionality. That's why I'm asking the community to share the source codes of your projects with us. Now let's speak of it all in detail. Continue: http://www.viva64.com/en/b/0184/

After a long wait C++Builder XE3 Update 1 has finally acquired the capability of building 64-bit applications. It means that developers using this tool will soon face the yet unfamiliar world of 64-bit errors.

Visual Studio provides very powerful capabilities for us to extend its functional using various technologies and approaches. You can both automate routine actions using simplest macros and carry out a deep integration of any third-party or your own user components. In fact, while extending Visual Studio, you are limited only by your own imagination, so you can realize such eccentric solutions as integration of your favorite Instant Messenger client into the project window, or even an "achievements for developers" ( http://visualstudiogallery.msdn.microsoft.com/bc7a433b-b594-48d4-bba2-a2f24774d02f ) system like in videogames! After all, any serious developer must know and be able to adjust the development environment to his/her own needs, as well as be able to handle its possible "glitches". At the same time, creating extensions is nowadays simple and transparent as never before, regardless of your previous experience of working with Visual Studio! You can both integrate a native library module that will be able to directly handle the low-level COM interfaces of the API environment, and a managed build that will have an access to almost all of these APIs through convenient managed wraps. While the native unit will surely provide the developer with the absolute control over the situation, using managed builds for extensions will help you get rid of a very complicated process of calculating the number of COM-objects instances and direct memory handling, allowing you to focus on implementing the functionality you need with all the power .NET Framework and Common Language Runtime can provide. If you've got interested in the subject of extending Visual Studio, you can try it right now starting with 3 simple steps described in this article. This guide will allow you to create a completely functional managed extension module for all the Visual Studio versions literally within 10 minutes and start using your functional at once, while the rest articles of this series

I'm joking about Linux, of course. Nevertheless, this question really interests me. I understand that systems they work on in Microsoft are large and complex. I know very well that bugs may be detected by users only some time later after release. But I don't understand how can one simply not notice obvious bugs in the tools the developers themselves are meant to use regularly?

In this article, I've collected a huge amount of links all of which could prove potentially useful to software developers who are getting acquainted with 64-bit world. In general, we will cover C/C++ languages, but I am sure, that developers from other languages will discover a lot of interesting stuff here as well.

The ReactOS project is rapidly developing. One of the developers participating in this project suggested that we re-analyzed the source code, as the code base is growing fast. We were glad to do that. We like this project, and we'll be happy if this article helps the developers to eliminate some bugs. Analysis was performed with the PVS-Studio 5.02 code analyzer.

This article covers the structure of Visual C++ project model (VCProject). Also included are the cases of using the project model for enumeration of project elements and obtaining their compilation properties through the corresponding configurations.

This article deals with creation, utilization and handling of Visual Studio commands in its extension modules through automation object model APIs and IDE services. The relations between IDE commands and environment UI elements, such as user menus and toolbars, will also be examined.

Program errors occurring while porting C++ code from 32-bit platforms on 64-bit ones are observed. Examples of the incorrect code and the ways to correct it are given. Methods and means of the code analysis which allow to diagnose the errors discussed, are listed.

Many programmers think that the more error messages a static code analyzer produces, the better. It would be true if all the messages hit the bull's eye, as they say. But this is impossible: the same warnings may be considered both true and false by different programmers depending on the project type. There is also one more important and interesting thing. It may appear that a line between a false positive and a real error is very thin. Let's have a look at one of these cases.

Much is said about good and harm of comments in program code and a single opinion hasn't been worked out yet. However, we've decided to take a look at comments from a different viewpoint. Can comments serve as an indication of hidden errors for a programmer studying the code?