Facebook Open source Flint: A C + + static code analyzer written in D language

Recently, http://www.aliyun.com/zixun/aggregation/1560.html ">facebook Open source flint--a c++++ Static code analyzer written in D language, That's more consistent with Facebook's style. Facebook Open Flint Software source code, not only through the user and the programmer's feedback to flint constantly update and improve the performance of flint.

Why not use existing lint tools?

Lint programs in the category of the program request is a strange type of program request, after a period of time for the use of lint, developers believe that the lint program to build the Facebook architecture does not have any obvious effect. At this point, the C + + static Code analyzer, written in D language,--flint into people's field of vision, and has attracted much attention due to its special performance and lightweight volume.

What is Flint?

To introduce one of Facebook's lint programs--flint, its main function is to automatically prompt for alert information. For example, give the appropriate code modification hints in the Code audit system, remind the programmer which line of code is wrong, and so on. Flint has become an essential and important helper of the work of Facebook programmers. This is why open source flint is necessary because any programmer can test the programs built by Facebook programmers and make suggestions for improvement. Frankly speaking, open source is also a test for programmers, do you dare to publish the bad code?

Flint is written in d language and is the first code base written by Facebook's Open source D language. In fact, the original version of Flint was written in C + +, and the Flint version that was rewritten in D was tested as an experimental version, but the developer finally found that the Flint version written in D was more lightweight, faster, more efficient and more easily shared.

Benefits from using Flint:

Check for blacklisted tag sequences.

Check blacklisted identifiers.

Check the reserved identifiers.

Check for suspicious target options.

Check all open source projects.

By referencing, you can catch all the exception information.

Eliminate common errors in defined architectures.

Check the space name directive that is being used.

A numeric value is used to detect the wrong string.

Suppress enforced operators that are hidden.

For open source Flint this matter, the developer is certainly more exciting, this is also "easiest design is easiest to succeed" the vivid portrayal, besides, this is the cross language most interesting transformation.