Sider Announces Recommended, a Coding Guide Built on Analyzing 1,000 Projects – CIOReview

Subscribe For The CIOReview Newsletter.

A weekly summary of the news, trends, reviews, profiles and articles from CIOReview

Email


     –  No, Thanks

Most Popular ( 1-4 of 8 )

32763

1

By CIOReview | Wednesday, January 13, 2021

The Recommended Guidelines for C/C++ analyzes (cpplint) for Sider are currently applicable. It is now being extended to Java, Ruby, and JavaScript languages. In due course, other languages are sponsored.

FREMONT, CA: Sider, a software development support tool developer and supplier, has developed the recommended code guide ‘Recommended Rules’ and incorporated them into its automated code review program.

By evaluating hundreds of current coding rules, this guide includes only the essential rules accompanied by many open-source projects and was established based on joint research with Professor Shingo Takada of the Department of Information Engineering, Faculty of Science and Technology, Keio University and Associate Professor Seigo Nakura of the Department of Software Engineering, Faculty of Science and Technology, Nanzan University.

The suggested rules were generated by the extraction of programming guides related to 1,000 renowned open-source software projects and the study of source code and the production history of them. Through implementing these new guidelines, the automatic code analysis of Sider creates recommendations of greater significance and value, which increases software development efforts efficiency.The Recommended Rules for C/C++ analyzes (cpplint) for Sider are currently applicable. It is now being extended to Java, Ruby, and JavaScript languages. In due course, other languages are sponsored.

Research Background

For the maintenance of high code quality in applications, the coding guides were developed and written. Adherence to these laws can provide advantages such as bug deterrence, more effortless reading and repair, and security vulnerability avoidance. However, there are also different rules in these multiple coding manuals. For example, there are standards with regulations that say the language should be employed in principle where “and” can be similarly used in programming languages.

Although it is expected that following regulations during implementation would promote the development team, it is not clear if it is worth the effort to extend these laws to code, which have already been completed. The decision is taken not to unify in specific teams/projects because it is of little value to efficiency.As a code guide useful for any project, the Recommended Rules have been created. It is easy to set up and run the guide according to the project by first incorporating this guide into a project and then providing for other required requirements according to the project.