<?xml version="1.0" encoding="windows-1251" ?>
<rss version="2.0">
	<channel>
		<title>News from www.viva64.com</title> 
		<link>http://www.viva64.com/</link> 
		<description>RSS News</description> 
		
		<language>en</language> 
		<copyright>Copyright 2008</copyright>
		<pubDate></pubDate>		
		<lastBuildDate></lastBuildDate>
		<docs>http://www.rssboard.org/rss-specification</docs>				 
		<generator></generator> 
		<managingEditor></managingEditor> 
		<webMaster></webMaster> 
		<ttl>60</ttl>		
		<item>
							  <title>We released a new version of PVS-Studio code analyzer - PVS-Studio 3.61</title>
							  <link>http://www.viva64.com/news/2010/07/22/72/</link> 
							  <description>&lt;P&gt;We released a new version of PVS-Studio code analyzer - PVS-Studio 3.61:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Fixed crash in VS2010 with EnableAllWarnings key enabled in project settings. &lt;/LI&gt;
&lt;LI&gt;Fixed bug related to analysis projects that does excluded from build in Configuration Manager. &lt;/LI&gt;
&lt;LI&gt;The analysis of the code is considerably improved.&lt;/LI&gt;&lt;/UL&gt;</description> 
							  <pubDate>Thu, 22 Jul 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/07/22/72/</guid>							  							  					   
						  </item><item>
							  <title>We released a new version of PVS-Studio code analyzer - PVS-Studio 3.60</title>
							  <link>http://www.viva64.com/news/2010/06/10/71/</link> 
							  <description>&lt;P&gt;We released a new version of PVS-Studio code analyzer - PVS-Studio 3.60:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;New rule &lt;A class=link-outer href=&quot;http://www.viva64.com/content/PVS-Studio-help-en/V122.html&quot; target=_blank&gt;V122&lt;/A&gt;: Memsize type is used in the struct/class. 
&lt;LI&gt;New rule &lt;A class=link-outer href=&quot;http://www.viva64.com/content/PVS-Studio-help-en/V303.html&quot; target=_blank&gt;V303&lt;/A&gt;: The function is deprecated in the Win64 system. It is safer to use the NewFOO function. 
&lt;LI&gt;New rule &lt;A class=link-outer href=&quot;http://www.viva64.com/content/PVS-Studio-help-en/V320.html&quot; target=_blank&gt;V320&lt;/A&gt;: A call of the FOO function will lead to a buffer overflow or underflow in a 64-bit system. 
&lt;LI&gt;New rule &amp;lt;A class=link-outer href&lt;/LI&gt;&lt;/UL&gt;</description> 
							  <pubDate>Thu, 10 Jun 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/06/10/71/</guid>							  							  					   
						  </item><item>
							  <title>Our workers visited the GDC2010 conference</title>
							  <link>http://www.viva64.com/news/2010/05/19/70/</link> 
							  <description>&lt;P&gt;Our workers visited the GDC2010 conference that was held on May, 14-16, 2010, in Moscow and talked to many developers who participated there.&lt;/P&gt;
&lt;P&gt;Game Developer Conference (GDC) is an official forum in Russian conducted “by developers for developers” and publishers of personal computer, play station, online and social network games as well as games for arcade machines, mobile phones and various other platforms. Recognized experts in various spheres of game development – from specifics of programming and character modeling to project management and after-sales maintenance – read about 100 lectures and seminars at GDC every year. Besides, the annual GDC exhibition Expo presents contemporary software, services and platforms for developers and also new game projects which have not been released on market yet.&lt;/P&gt;While communicating with developers from the game industry, we again get convinced that 64-bit technologies are still of little interest for those who develop games to be installed on a user computer. 64 bits are already being widely used on the server side in mass multiplayer online role play games (MMORPG). But developers do not plan to create 64-bit versions of their games until 99% of users have a 64-bit Windows version installed.</description> 
							  <pubDate>Wed, 19 May 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/05/19/70/</guid>							  							  					   
						  </item><item>
							  <title>We released a new version of PVS-Studio code analyzer - PVS-Studio 3.53</title>
							  <link>http://www.viva64.com/news/2010/05/07/69/</link> 
							  <description>&lt;P&gt;We released a new version of PVS-Studio code analyzer - PVS-Studio 3.53:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&quot;What Is It&quot; feature is added. Now you can ask PVS-Studio developers about diagnistic messages produced by our analyzer. &lt;/LI&gt;
&lt;LI&gt;The analysis of the code related to usage of unnamed structures is considerably improved. &lt;/LI&gt;
&lt;LI&gt;Fixed bug in structure size evaluation in certain cases.&lt;/LI&gt;&lt;/UL&gt;</description> 
							  <pubDate>Fri, 07 May 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/05/07/69/</guid>							  							  					   
						  </item><item>
							  <title>We released a new version of PVS-Studio code analyzer - PVS-Studio 3.52</title>
							  <link>http://www.viva64.com/news/2010/04/27/68/</link> 
							  <description>&lt;P&gt;We released a new version of PVS-Studio code analyzer - PVS-Studio 3.52.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;New online help has been added. The previous help system integrated &lt;BR&gt;into MSDN. It was not very convenient for some reasons (both for us &lt;BR&gt;and users). Now PVS-Studio will open the help system on our site. We &lt;BR&gt;refused to integrate it into MSDN anymore. As before, the pdf-version &lt;BR&gt;of the documentation is also available. 
&lt;LI&gt;We stopped supporting Windows 2000. 
&lt;LI&gt;The settings page &quot;Exclude From Analysis&quot; was deleted â€“ there is now &lt;BR&gt;the page &quot;Don't Check Files&quot; instead. 
&lt;LI&gt;Work in Visual Studio 2010 was improved. 
&lt;LI&gt;We eliminated the issue of integration into VS2010 whenreinstalling. 
&lt;LI&gt;We fixed work of the function &quot;Mark As False Alarm&quot; with read-only&lt;BR&gt;files. &lt;/LI&gt;&lt;/UL&gt;</description> 
							  <pubDate>Tue, 27 Apr 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/04/27/68/</guid>							  							  					   
						  </item><item>
							  <title>We released a new version of PVS-Studio code analyzer - PVS-Studio 3.51</title>
							  <link>http://www.viva64.com/news/2010/04/16/67/</link> 
							  <description>&lt;P&gt;We released a new version of PVS-Studio code analyzer - PVS-Studio 3.51.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;PVS-Studio supports Visual Studio 2010 RTM.&lt;/LI&gt;
&lt;LI&gt;New rule: V003: Unrecognized error found...&lt;/LI&gt;
&lt;LI&gt;New rule: V121: Implicit conversion of the type of 'new' operator's argument to size_t type.&lt;/LI&gt;
&lt;LI&gt;You may specify filemasks on the tab &quot;Don't Check Files&quot; to exclude some files from analysis.&lt;/LI&gt;
&lt;LI&gt;&quot;Exclude From Analysis&quot; option page improved&lt;/LI&gt;
&lt;LI&gt;MoreThan2Gb option removed from &quot;Viva64&quot; option page (this option is deprecated)&lt;/LI&gt;
&lt;LI&gt;If you want check code from command line then you must indicate analyzer type (Viva64 or VivaMP)&lt;/LI&gt;&lt;/UL&gt;</description> 
							  <pubDate>Fri, 16 Apr 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/04/16/67/</guid>							  							  					   
						  </item><item>
							  <title>A new version of the code analyzer PVS-Studio 3.50 is released</title>
							  <link>http://www.viva64.com/news/2010/03/26/66/</link> 
							  <description>&lt;P&gt;We released a new version of PVS-Studio code analyzer - PVS-Studio 3.50. There are seven important innovations in the new version each of which is very useful.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;PVS-Studio supports Visual Studio 2010 RC. Although Visual Studio has not been released officially yet, we have already added the support for this environment into the analyzer. Now PVS-Studio integrates into Visual Studio 2010 and can analyze projects in this environment. Help system in Visual Studio 2010 has been changed, so the Help section of PVS-Studio does not integrate into the documentation yet as it is done in Visual Studio 2005/2008. But you still may use &lt;A href=&quot;http://www.viva64.com/content/PVS-Studio-help-en/contents.html&quot;&gt;online-Help&lt;/A&gt;. Support of Visual Studio 2010 RC is not complete.&lt;/LI&gt;
&lt;LI&gt;A new PDF-version of Help system is available. Now we ship a 50-page PDF-document in the PVS-Studio distribution kit. It is a full copy of our Help system (that integrates into MSDN in Visual Studio 2005/2008 and is available online).&lt;/LI&gt;
&lt;LI&gt;PVS-Studio now has a new mechanism that automatically checks for new versions of the tool on our site. Checking for the updates is managed through the new option &lt;I&gt;CheckForNewVersions&lt;/I&gt; in the settings tab called &quot;Common Analyzer Settings&quot;. If the option &lt;I&gt;CheckForNewVersions&lt;/I&gt; is set to True, a special text file is downloaded from &lt;A href=&quot;http://www.viva64.com/&quot;&gt;www.viva64.com&lt;/A&gt; site when you launch code testing (the commands Check Current File, Check Current Project, Check Solution in PVS-Studio menu). This file contains the number of the latest PVS-Studio version available on the site. If the version on the site is newer than the version installed on the user computer, the user will be asked for a permission to update the tool. If the user agrees, a special separate application PVS-Studio-Updater will be launched that will automatically download and install the new PVS-Studio distribution kit. If the option &lt;I&gt;CheckForNewVersions &lt;/I&gt;is set to False, it will not check for the updates.&lt;/LI&gt;
&lt;LI&gt;We have implemented the support for the standard C++0x at the level it was done in Visual Studio 2010. Now it supports lambda expressions, auto, decltype, static_assert, nullptr, etc. In the future, as C++0x support in Visual C++ is developing, the analyzer PVS-Studio will also provide support for the new C++ language capabilities.&lt;/LI&gt;
&lt;LI&gt;Now you can check solutions with PVS-Studio from the command line instead of Visual Studio environment. Note that we still mean that the checking will be performed from Visual Studio involving the files of projects (.vcproj) and solutions (.sln) but it will be launched from the command line instead of IDE. This way of launching the tool may be useful when you need to regularly check the code with the help of build systems or continuous integration systems.&lt;/LI&gt;
&lt;LI&gt;New rule V1212: Data race risk. When accessing the array 'foo' in a parallel loop, different indexes are used for writing and reading.&lt;/LI&gt;
&lt;LI&gt;We added a code signature certificate in the new version of our tool. It is done for you to be sure that the distribution kit is authentic, and get fewer warnings from the operating system when installing the application.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;We hope that both our current and new users will like the new version of PVS-Studio tool.&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description> 
							  <pubDate>Fri, 26 Mar 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/03/26/66/</guid>							  							  					   
						  </item><item>
							  <title>New design of our site</title>
							  <link>http://www.viva64.com/news/2010/03/15/64/</link> 
							  <description>&lt;P&gt;We have developed and introduced a new design for the site www.viva64.com. We proceeded from the following tasks while developing it:&lt;/P&gt;
&lt;OL type=1&gt;
&lt;LI&gt;To simplify the site navigation and make the site sections more comprehensible.&lt;/LI&gt;
&lt;LI&gt;To simplify the access to those site sections devoted to the code analyzer PVS-Studio. Now you may go to the page of downloading or purchasing the analyzer and see the documentation on the program from any page.&lt;/LI&gt;
&lt;LI&gt;To present the information that would be useful not only for PVS-Studio users but for all application developers in a more convenient and clear form. Now you may get from any site page through a special menu &quot;For Developers&quot; to the sections &quot;Our Articles&quot;, &quot;64-bit Lessons&quot; (lessons of 64-bit software development), &quot;Knowledge Base&quot; (the knowledge base of issues related to 64-bit and parallel software development), &quot;Terminology&quot; (special terms used in the articles), &quot;Article Reviews&quot; (our reviews of third-party papers published on the Internet), &quot;Blog&quot; (our notes on software development).&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;We hope that we have fulfilled these tasks by introducing the new design. This is how our site looked before:&lt;/P&gt;
&lt;P&gt;&lt;IMG alt=&quot;&quot; src=&quot;http://www.viva64.com/usr/templates/images/1268655258662.png&quot; border=0&gt;&lt;/P&gt;
&lt;P&gt;This is the new design:&lt;/P&gt;
&lt;P&gt;&lt;IMG alt=&quot;&quot; src=&quot;http://www.viva64.com/usr/templates/images/1268655322796.png&quot; border=0&gt;&lt;/P&gt;
&lt;P&gt;Please tell us if there are some troubles with the new design or if you find some innovations inconvenient.&lt;/P&gt;</description> 
							  <pubDate>Mon, 15 Mar 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/03/15/64/</guid>							  							  					   
						  </item><item>
							  <title>We have a knowledge base of issues related to 64-bit and parallel software development at our site</title>
							  <link>http://www.viva64.com/news/2010/03/12/63/</link> 
							  <description>&lt;P&gt;The main method of promoting our program product &lt;A href=&quot;http://www.viva64.com/pvs-studio/&quot;&gt;PVS-Studio&lt;/A&gt; is to tell the developers about the type issues this tool can solve.&lt;/P&gt;
&lt;P&gt;&lt;I&gt;Note. PVS-Studio is an add-in module for Visual Studio 2005/2008 (and 2010 soon) that allows you to detect a lot of various errors in 64-bit and parallel OpenMP applications. PVS-Studio is a contemporary interactive static C/C++ code analyzer. By 'interactive', for instance, we mean the capability of warning filtration and suppression without relaunching the analysis.&lt;/I&gt;&lt;/P&gt;
&lt;P&gt;The main way of promoting our tool is to write and publish technical papers on various programmer sites, for example: CodeProject, Intel Software Network, DreamInCode. Of course, all our &lt;A href=&quot;http://www.viva64.com/articles/&quot;&gt;articles&lt;/A&gt; are available on our site as well.&lt;/P&gt;
&lt;P&gt;We found out with time that not every idea/material may be conveniently presented in the form of an article. Some notes were too small and could not pretend to be papers while we did not want to enlarge them artificially. Some other notes concerned only one particular feature of PVS-Studio and did not tend to be papers too. So we decided to create a &lt;A href=&quot;http://www.viva64.com/blog/en/&quot;&gt;blog&lt;/A&gt; on our site and have been publishing various ideas there since that moment.&lt;/P&gt;
&lt;P&gt;Absence of explanations of some terms that could be not quite clear to the readers appeared to be another drawback of our articles. But links and notes overload the text and break the coherence of the articles. We found the way out by creating the section &lt;A href=&quot;http://www.viva64.com/articles/terminology/&quot;&gt;terminology&lt;/A&gt; on our site where you may find a lot of explanations and definitions and additional links to external resources.&lt;/P&gt;
&lt;P&gt;But we did stop classification of our materials there. Not so long ago we created a new section called &quot;&lt;A href=&quot;http://www.viva64.com/articles/knowledge/&quot;&gt;knowledge base &lt;/A&gt;&quot;. Here we lay out materials concerning particular questions developers ask when creating 64-bit and parallel software. There are few notes in the base for the present, but we will regularly enlarge it and in some time you will be able to find answers to many most urgent questions there. Now you may see the following posts:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/error_C2440_OnTimer.html&quot;&gt;A common error occurring when compiling a 64-bit application: error C2440, OnTimer&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/error_C4235_Assembler.html&quot;&gt;A common error occurring when compiling a 64-bit application: error C4235, Assembler&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/size_t_vs_uintptr_t.html&quot;&gt;Are the types size_t and uintptr_t equivalent?&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/WPARAM_UINT_LPARAM_LONG.html&quot;&gt;Confusion of WPARAM with UINT, and LPARAM with LONG&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/printf_p_x_size.html&quot;&gt;Difference between %p and %x&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/ntohl_htonl_64_bit_value.html&quot;&gt;Functions of the ntohl/htonl class and 64-bit values&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/size_t_32_64.html&quot;&gt;Is there a way to make the type size_t 32-bit in a 64-bit program?&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/MSDN_64_bit_issues.html&quot;&gt;Obsolete descriptions of functions in MSDN taking no account of 64 bits&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/error_C2664.html&quot;&gt;Strange errors occurring when compiling the 64-bit version of an application, error C2664&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/D9040.html&quot;&gt;Visual Studio Team System, /analyze and D9040&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/waring_C4267_unsigned_string_find.html&quot;&gt;Warning C4267 in the expression unsigned n = str.find(substr)&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/64_bit_compiler_Visual_Studio.html&quot;&gt;Where is the 64-bit compiler in Visual Studio?&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/WoW64_redirection.html&quot;&gt;Why does WoW64 use register and file system redirection?&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href=&quot;http://www.viva64.com/knowledge/size_t_prinft_scanf.html&quot;&gt;Working with the type size_t in the functions prinft, scanf and similar functions&lt;/A&gt;&lt;/LI&gt;&lt;/OL&gt;</description> 
							  <pubDate>Fri, 12 Mar 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/03/12/63/</guid>							  							  					   
						  </item><item>
							  <title>Reviews of articles on static analysis, 64-bit and parallel programming</title>
							  <link>http://www.viva64.com/news/2010/02/11/62/</link> 
							  <description>
&lt;!--
&lt;p&gt;
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;/li&gt;
    &lt;li&gt;&lt;/li&gt;
    &lt;li&gt;&lt;/li&gt;
    &lt;li&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;a href=&quot;&quot;&gt;&lt;/a&gt;
--&gt;
&lt;p&gt;
Do you want to be abreast of the articles written by the authors all over the world on the most contemporary topics (static analysis, 64-bit and parallel programming)? Do you want to know what articles you should read first? We have a new section &quot;&lt;a href=&quot;http://www.viva64.com/links/&quot;&gt;Article reviews&lt;/a&gt;&quot; on our site viva64.com.
&lt;/p&gt;
&lt;p&gt;
While carrying out investigations in the sphere of developing tools for 64-bit and parallel software developers, we, naturally, study publications by various authors on these topics. But people interested in them find it difficult to get familiar with all the articles because one has to look for them somewhere and it is not very easy.
&lt;/p&gt;
&lt;p&gt;
That is why we decided to make brief reviews (up to 2 paragraphs) for these articles. These are neither abstracts, nor author-generated summaries and nor user-generated content. The reviews of the articles are written by our colleagues who are always involved in this sphere.
&lt;/p&gt;
&lt;p&gt;
All the article reviews are arranged in three groups:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;&lt;a href=&quot;http://www.viva64.com/links/64-bit-development/&quot;&gt;64-bit Development&lt;/a&gt;&lt;/li&gt;
    &lt;li&gt;&lt;a href=&quot;http://www.viva64.com/links/parallel-programming/&quot;&gt;Parallel Programming&lt;/a&gt;&lt;/li&gt;
    &lt;li&gt;&lt;a href=&quot;http://www.viva64.com/links/code-analyzers/&quot;&gt;Code Analyzers&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Here are some examples of the reviews.
&lt;/p&gt;
&lt;a href=&quot;http://www.viva64.com/go.php?url=24&quot;&gt;64-Bit Programming Models: Why LP64.&lt;/a&gt;
&lt;p&gt;
In the world of rapidly developing programming technologies it is important for all software developers to decide what standard and programming model to choose as universal to save time and money. The Open Group argues that LP64 programming model be the best solution for 64-bit programming. This conclusion is drawn from the results of analysis and comparison of ILP64 and LP64 models against several evaluation criteria, each being thoroughly commented and explained. Among these the authors list portability, interoperability with 32-bit environments, standards conformance, performance effects and transition costs.
&lt;/p&gt;
&lt;a href=&quot;http://www.viva64.com/go.php?url=127&quot;&gt;Herb Sutter. The Free Lunch Is Over: A Fundamental Turn Toward Concurrency in Software.&lt;/a&gt;
&lt;p&gt;
In his article, Herb Sutter discusses the problem of concurrency becoming the next approaching revolution for software development, its causes, consequences and costs. A major part of the paper is devoted to analyzing the current state in the computer industry and explaining why sequential applications cannot benefit from the throughput gains any more and must yield to concurrent (mainly multithreaded) software; and how to deal with this problem as well. The paper is written in a lively and ironical manner but provides a truly serious and thorough review of the coming changes. Sure, it will be interesting and helpful for every developer.
&lt;/p&gt;
&lt;a href=&quot;http://www.viva64.com/go.php?url=247&quot;&gt;Raoul Jetley, Ben Chelf. Diagnosing Medical Device Software Defects Using Static Analysis&lt;/a&gt;
&lt;p&gt;
Nowadays, when medicine employs complex devices for treating patients, software used in them must be secured from any defects and bugs. The paper concerns static analysis of such software systems. There are several sections that describe the essence of static analysis method, defect classes both common for software development on the whole and specific for medical devices, the task of choosing the best static code analysis tool and factors to consider while making this choice.
&lt;/p&gt;
&lt;p&gt;
All the article reviews contain links to the source articles. We hope that our reviews will help you become more aware of the state of this sphere today.
&lt;/p&gt;
        </description> 
							  <pubDate>Thu, 11 Feb 2010 10:00:00 +0300</pubDate>
							  <guid>http://www.viva64.com/news/2010/02/11/62/</guid>							  							  					   
						  </item>
	</channel>
</rss>