有很多的代码分析(FxCop)警告。
静态代码分析可以帮助你找出你软件中可能的代码错误。
Static code analysis can help you to figure out the possible coding errors in your software.
工作空间层是对整个解决方案执行代码分析和重构的起点。
The workspace layer is the starting point for doing code analysis and refactoring over entire solutions.
文章中包含了完整的示例源代码,并带有逐行的代码分析。
Complete source code examples will be included, with line-by-line analysis of what the code is doing.
用于文档编制、编译器检查和代码分析的工具可以使用这些额外信息。
This additional information is used by tools for the purposes of documentation, compiler checking, and code analysis.
一般来说,元数据的好处分为三类:文档编制、编译器检查和代码分析。
In general, metadata's benefits fall into three categories: documentation, compiler checking, and code analysis.
代码复查:一个静态代码分析工具可以分析你的代码并报告其中的错误。
Code Review: a static code analysis tool that analyzes your code and reports problems.
在测量工具部分,Jaibeer解释了使用静态代码分析工具的理由。
In the Measurement tools part, Jaibeer explains the reasons to use static code analysis tools.
代码分析应在开发的早期阶段进行,或将其作为开发后的第一个性能测试。
Code profiling should be done in the early stages of development, or as a first performance test after development.
RubyMine可以在输入代码时进行即时代码分析,并高亮提示错误。
RubyMine performs code analysis as code is typed, highlighting errors.
每个人都用运行时调试器调试过代码,或者用代码分析工具找过执行热点。
Everyone has debugged code with a runtime debugger or found performance hotspots with a code profiler.
它让你使用代码分析器分析ActionScript代码,这是一个好的开始。
This allows you to use the code analyzer on your ActionScript code, so that is a good start.
第一步,利用静态代码分析器浏览代码并搜索反模式,以确保遵循良好的编码实践。
As a first step, employ static code analyzers that will go through your code and search for anti-patterns to ensure that good coding practices have been followed.
静态代码分析,在Windows平台上长期受到忽视,近几年却变得越来越重要。
Static code analysis, long neglected on the Windows platform, has been becoming more and more import in the last few years.
因为我们的过程的第三个步骤处理实际的代码分析,所以在RUP中没有等价的规程。
Since the third step of our process deals with actual code analysis, there is no equivalent discipline in RUP.
这种类型的残留代码也可以通过静态代码分析工具如pmd和FindBugs找到。
This sort of vestigial code can also be found by static code analysis tools like PMD and FindBugs.
独一无二的C#代码分析功能——随时随地查找并高亮标识错误,并且提供代码建议;
Unique Code Analysis for C# - finds and highlights errors on the fly and offers code suggestions
SQLite使用全面覆盖的测试来保证质量,而不是依靠编译器警告或静态代码分析工具。
Quality assurance in SQLite is done using full-coverage testing, not by compiler warnings or other static code analysis tools.
本文的目的是逐渐地让您适应自动的代码分析,并且介绍一些为您的软件开发过程带来的好处。
The goals are to gently ease you into automated code analysis and to present some of the benefits that this can bring to your software development process.
清单9给出了用清单8中的代码分析清单1、清单2和清单3中代码的完整结构所生成的输出。
Listing 9 gives the output generated by using the Listing 8 code to analyze the full structure of the code from Listing 1, Listing 2, and Listing 3.
一种更精确的测量——甚至可以测量运行单个源代码语句的时间——可以采用代码分析器。
A far more accurate measure — one that can even gauge the time taken to run a single-source code statement — can be taken using a code profiler.
SQLServer最佳实践分析器是专门为开发人员提示实践方面的问题的一个代码分析器。
The SQL Server Best practices Analyzer is a code analysis tool specifically written to warn developers about questionable practices.
微软的程序经理Duke Kamstra写过一篇介绍如何进行代码分析和代码度量的网志。
Duke Kamstra, Program Manager for Microsoft, has a walk-through on his Code Analysis and Code Metrics blog.
如果你对该工具有什么意见和建议,可以通过微软提供的VS代码分析和代码度量论坛参与讨论。
Feedback to Microsoft can be provided on the VS Code Analysis and Code Metrics forum.
已经存在一些源代码分析与字节代码分析以及哪种分析提供更好结果的比较,但是该讨论超出了本文的范围。
There has been some analysis of source code versus byte code analysis and which provides the better results, but that discussion is beyond the scope of this article.
进行全面性能测试之前,请考虑使用代码分析工具对应用程序进行分析,以发现潜在的效率低下问题和瓶颈问题。
Before moving into full performance testing, consider using a code profiling tool to analyze the application for potential inefficiencies and bottlenecks.
为静态代码分析工具(如FindBugs)编写自定义bug检测器可以显著提高代码质量,并且有许多乐趣。
Writing custom bug detectors for a static code analysis tool such as FindBugs can offer tremendous leverage in improving code quality, and it can be a lot of fun.
联机桌面允许开发人员在签入之前进行本地代码分析,并且可以保证具有和集成构建分析相同的准确性和上下文环境。
The connected desktop allows the developer to analyze their code locally before check in and with exactly the same accuracy and context as during integration build analysis.
在这两种情况中,元数据可以指示代码分析工具,虽然参数类型是Object,但Integer才是真正需要的。
In both cases, metadata can instruct a code-analysis tool that although the parameter type is Object, an Integer is what's really desired.
Ruby_parser还能提供抽象语法树节点的源码位置,这是Ruby代码分析或者 代码转换工具的必需信息。
Ruby_parser also provides source locations of AST nodes, which is obviously necessary for code analysis or code transformation tools in Ruby.
应用推荐