Method for reducing Android project code repetition degree

Abstract

The invention provides a method for reducing Android project code repetition degree, and belongs to the technical field of project code repetition degree reduction. The method includes: enabling Android project code to adopt a section-oriented programming method, and inserting a non-functional code into a compiled code; starting confusion and configuring a confusion dictionary; modifying paths ofcode files which are not confused in batches by using a Java script, and modifying naming formats of the entity class and Android component folders in batches by using the Java script; writing a Javascript program to add characters to the ends of all files in the project, and adding different characters to project files of different file formats; modifying a path where the project package is located; and when any directory of the project is positioned, newly creating a new signature file under the any directory, and when the App is packaged, using the signature file to perform signature. Compared with a method for directly modifying codes, the method for reducing the Android project code repetition degree has the advantages of being small in workload, capable of preventing generation of new bugs and the like.

Description

technical field [0001] The invention belongs to the technical field of reducing the repetition degree of project codes, and in particular relates to a method for reducing the repetition degree of Android project codes. Background technique [0002] With the rapid development of Internet technology, there are currently a large number of excellent programmers working on the development and application of various software. When developing projects, especially very large projects, programmers will face the problem of implementing specific functions written in the early stage of the project. Code blocks and code blocks of other functions are packaged together. As the number of packages increases, the data exchange between the code of the specific function and various code blocks becomes increasingly close. However, this application scenario will lead to when the software is put on the shelf, because If the repetitiveness of the software exceeds a certain limit, it will fail the r...

AI Technical Summary

Problems solved by technology

[0002] With the rapid development of Internet technology, there are currently a large number of excellent programmers working on the development and application of various software. When developing projects, especially very large projects, programmers will face the problem of implementing specific functions written in the early stage of the project. Code blocks and code blocks of other functions are packaged together. As the number of packages increases, the data exchange between the code of the specific function and various code blocks becomes increasingly close. However, this application scenario will lead to when the software is put on the shelf, because The repetitiveness of the software exceeds a certain limit, resulting in unqualified review, but if the repeated code is modified, it may lead to instability of the entire software function, resulting in an increase in bugs, and even the collapse of the entire software

At present, programmers generally use one person to write the code of related functions to reduce code repetition, and try to reduce an independent functional module to be written by multiple people. In addition, the smallest module method is used when packaging, and more complex functions are packaged with the smallest module. module

The disadvantage of this method is that when the project code is very large, it is impossible for one person to complete the writing of a certain function code alone, and encapsulating it with the smallest module will also cause more code duplication, and even more cause when the duplication is detected. The high degree of code repetition leads to listing failures. In addition, if the project code is directly modified, new bugs may be generated, resulting in program instability and even project failure.

This solution proposes a solution to the problem of failure to pass the review due to the high repetition of software codes caused by too many packaging times during the software review process. It has the advantages of simple method and no bug introduction.