Developing for iOS and Android | Code by Coffee. Free source code hosting – Bitbucket. List of tools for static code analysis. This is a list of tools for static code analysis. Language[edit] Multi-language[edit] .NET[edit] JavaScript[edit] Google's Closure Compiler – JavaScript optimizer that rewrites code to be faster and smaller, and checks use of native JavaScript functions.JSHint – A community driven fork of JSLint.JSLint – JavaScript syntax checker and validator. Objective-C, Objective-C++[edit] Clang – The free Clang project includes a static analyzer. Opa[edit] Packaging[edit] Lintian – Checks Debian software packages for common inconsistencies and errors.Rpmlint – Checks for common problems in rpm packages.
Perl[edit] PHP[edit] RIPS – A static code analyzer and audit framework for vulnerabilities in PHP applications. PL/SQL[edit] TOAD - A PL/SQL development environment with a Code xPert component that reports on general code efficiency as well as specific programming issues. Pylint – Static code analyzer. Formal methods tools[edit] See also[edit] References[edit] External links[edit] Pro Git 1.3 Getting Started Git Basics. So, what is Git in a nutshell? This is an important section to absorb, because if you understand what Git is and the fundamentals of how it works, then using Git effectively will probably be much easier for you.
As you learn Git, try to clear your mind of the things you may know about other VCSs, such as Subversion and Perforce; doing so will help you avoid subtle confusion when using the tool. Git stores and thinks about information much differently than these other systems, even though the user interface is fairly similar; understanding those differences will help prevent you from becoming confused while using it. Snapshots, Not Differences The major difference between Git and any other VCS (Subversion and friends included) is the way Git thinks about its data. Conceptually, most other systems store information as a list of file-based changes. Figure 1-4. Git doesn’t think of or store its data this way. Figure 1-5. Nearly Every Operation Is Local Git Has Integrity The Three States. Explore GitHub - GitHub. Gist. Features / Community - GitHub. Regular Expressions Reference - Basic Syntax.
The regular expressions reference on this website functions both as a reference to all available regex syntax and as a comparison of the features supported by the regular expression flavors discussed in the tutorial. The reference tables pack an incredible amount of information. To get the most out of them, follow this legend to learn how to read them. The tables have six columns for each regular expression feature. The first four explain the feature. The final two columns indicate whether your two chosen regular expression flavors support this particular feature. You can change the flavors using the drop-down lists above the table. When this legend says "all versions" or "no version", that means all or none of the versions of each flavor that are covered by the reference tables: For the .NET flavor, some features are indicated with "ECMA" or "non-ECMA".
For the std::regex and boost::regex flavor there are additional indicators ECMA, basic, extended, grep, egrep, and awk.