Code warehouse system based on labels

Abstract

The invention discloses a code warehouse system based on labels. The code warehouse system comprises a front-end user module, a search engine and a code warehouse, the front-end user module is used for monitoring an operation instruction of the integrated development environment; the search engine is used for searching a code warehouse according to the operation instruction so as to obtain a target code fragment and a target code label corresponding to the operation instruction, and sending the target code fragment and the target code label to the front-end user module for the integrated development environment to display; and the front-end user module is used for inserting the target code snippet into the code file according to a further operation instruction after display. The system hasthe technical effects that the code warehouse is retrieved by monitoring the user operation, and the corresponding code snippets and code tags are obtained and inserted into the code files, so that on one hand, the computer resources are saved, the computing power requirement of compiling is reduced, and on the other hand, resource waste caused by function addressing is avoided, and on the otherhand, code insertion of the logic content is realized.

Description

technical field [0001] The invention relates to software development, in particular to a tag-based code warehouse system. Background technique [0002] In traditional code editing work, code reuse is generally achieved through function calls. For example, if a function is used very frequently, it is used as a part of the library. Taking the C++ standard library as an example, it is easy to encapsulate A large number of commonly used functions, such as input and output, data structure and other common functions, are called for use. However, due to the method of calling the function, there are the following disadvantages: [0003] (1) Based on the principle of the compilation and operation process itself, if there are too many functions, it will waste a lot of resources in the process of function addressing; [0004] (2) Since the library it calls often has not only the required parts, but also a large number of parts that are not actually needed, the code needs to consume a...

AI Technical Summary

Problems solved by technology

[0003] (1) Based on the principle of the compilation and operation process itself, if there are too many functions, it will waste a lot of resources in the process of function addressing;

[0004] (2) Since the library it calls often has not only the required parts, but also a large number of parts that are not actually needed, the code needs to consume a lot of resources on the parts we don't need before running and compiling

[0005] Based on the above reasons, in the actual process, the method of code insertion is often used, that is to say, the content logic of the code is directly written into the source file to avoid the above problems, but this method is often intelligently designed and simple, such as if, Switch And other logical branch architectures cannot be applied to complex code logic. Taking Visual Studio as an example, it is limited to the insertion of simple code structures and does not involve code content.

Images