CN114443128A - Language element analysis method and device, electronic equipment and storage medium - Google Patents
Language element analysis method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114443128A CN114443128A CN202011190547.4A CN202011190547A CN114443128A CN 114443128 A CN114443128 A CN 114443128A CN 202011190547 A CN202011190547 A CN 202011190547A CN 114443128 A CN114443128 A CN 114443128A
- Authority
- CN
- China
- Prior art keywords
- source code
- preset
- lines
- line
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 106
- 238000012545 processing Methods 0.000 claims abstract description 107
- 238000000034 method Methods 0.000 claims abstract description 83
- 230000006870 function Effects 0.000 claims description 32
- 238000004590 computer program Methods 0.000 claims description 11
- 230000014509 gene expression Effects 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 16
- 230000008859 change Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 6
- 238000012217 deletion Methods 0.000 description 5
- 230000037430 deletion Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000007667 floating Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000002407 reforming Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 239000011800 void material Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 210000003000 inclusion body Anatomy 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/205—Parsing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the disclosure discloses a method and a device for analyzing language elements, electronic equipment and a storage medium. The method comprises the steps of acquiring a source code file of a preset programming language, and adding a line number in each line of source codes of a plurality of lines of source codes included in the source code file, wherein the line number can be used as auxiliary information to better distinguish each line of source codes. In addition, on the basis, the preset paragraphs in the multi-line source codes are recognized, and the preset paragraphs are replaced by the first preset marks, so that the influence of the preset paragraphs on the analysis of the language elements is reduced. Furthermore, preset symbols in multiple lines of source codes are identified, and single-line processing is carried out on the part of the source codes associated with the preset symbols, so that the same linguistic element can be distributed in the same line, and the situation that the analysis of the linguistic element is influenced because the same linguistic element is distributed in multiple lines is avoided. Furthermore, the language elements are identified on the basis of the source codes of multiple lines after single-row processing, and the method for extracting the language elements from the source codes more accurately is realized.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for analyzing a linguistic element, an electronic device, and a storage medium.
Background
Computer programs in the prior art may be source code written in a particular programming language. From source code to execution, it needs to go through stages of preprocessing, compiling, linking, running, etc.
A programming language includes a variety of elements, such as basic elements of classes, variables, enumerations, functions, and so on. Elements of a programming language may be referred to simply as language elements or morphemes.
The language elements in the prior art can be applied in various ways, but the language elements are difficult to be extracted from the source code.
Disclosure of Invention
In order to solve the technical problem or at least partially solve the technical problem, embodiments of the present disclosure provide a method, an apparatus, an electronic device, and a storage medium for analyzing a language element, so as to implement a method capable of extracting a language element from a source code more accurately.
The embodiment of the disclosure provides a method for analyzing a linguistic element, which comprises the following steps:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining language elements in the plurality of lines of source code after the single-serialization processing.
The embodiment of the present disclosure further provides a method for analyzing a linguistic element, including:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining annotations in the plurality of lines of source code after the single serialization processing and language elements related to the annotations;
and displaying the interface element corresponding to the language element in the user interface.
The embodiment of the present disclosure further provides a language element analysis device, including:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a source code file of a preset programming language, and the source code file comprises a plurality of lines of source codes;
the line number adding module is used for adding a line number in each line of source codes of the plurality of lines of source codes;
an identification module for identifying a preset paragraph in the plurality of lines of source code to which the line number is added;
the replacing module is used for replacing a preset paragraph in the multi-line source code with a first preset identifier;
the identification module is further configured to: on the basis that the replacement module replaces preset paragraphs in the multiple lines of source codes with the first preset identifications, recognizing preset symbols in the multiple lines of source codes;
the processing module is used for performing single-line processing on part of the source codes associated with the preset symbols in the multiple lines of source codes;
a determining module for determining the language elements in the plurality of lines of source code after the single-line processing.
The embodiment of the present disclosure further provides a language element analysis device, including:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a source code file of a preset programming language, and the source code file comprises a plurality of lines of source codes;
the line number adding module is used for adding a line number in each line of source codes of the plurality of lines of source codes;
an identification module for identifying a preset paragraph in the plurality of lines of source code to which the line number is added;
the replacing module is used for replacing a preset paragraph in the multi-line source code with a first preset identifier;
the identification module is further configured to: on the basis that the replacement module replaces preset paragraphs in the multiple lines of source codes with the first preset identifications, recognizing preset symbols in the multiple lines of source codes;
the processing module is used for performing single-line processing on part of the source codes associated with the preset symbols in the multiple lines of source codes;
a determining module, configured to determine an annotation in the plurality of lines of source code after the single-serialization processing and a language element related to the annotation;
and the display module is used for displaying the interface elements corresponding to the language elements in the user interface.
An embodiment of the present disclosure further provides an electronic device, including:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the linguistic element analysis method as discussed above.
The disclosed embodiments also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the linguistic element analysis method described above.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages: according to the language element analysis method provided by the embodiment of the disclosure, by acquiring the source code file of the preset programming language, a line number is added in each line of source codes of a plurality of lines of source codes included in the source code file, and the line number can be used as auxiliary information to better distinguish each line of source codes. In addition, on the basis, the preset paragraphs in the multi-line source codes are recognized, the preset paragraphs are replaced by the first preset marks, and the influence of the preset paragraphs on the linguistic element analysis can be reduced by replacing the preset paragraphs with the first preset marks because the preset paragraphs are likely to be long and the first preset marks are short. Further, on the basis that the preset paragraphs in the multi-line source code are replaced by the first preset marks, the preset symbols in the multi-line source code are recognized, and single-line processing is performed on the part of the source code associated with the preset symbols, so that the same linguistic element can be distributed in the same line, and the influence on analysis of the linguistic element caused by the fact that the same linguistic element is distributed in multiple lines is avoided. Furthermore, the language elements are identified on the basis of the source codes of multiple lines after single-row processing, so that the method for extracting the language elements from the source codes more accurately is realized.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
FIG. 1 is a flow chart of a method of linguistic element analysis in an embodiment of the present disclosure;
FIG. 2 is a flow diagram of another method of linguistic element analysis in an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of an application scenario in an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a user interface in an embodiment of the present disclosure;
FIG. 5 is a flow diagram of another method of linguistic element analysis in an embodiment of the present disclosure;
FIG. 6 is a flow diagram of another method of linguistic element analysis in an embodiment of the present disclosure;
FIG. 7 is a schematic structural diagram of a linguistic element analysis device in an embodiment of the present disclosure;
FIG. 8 is a schematic structural diagram of another linguistic element analysis device in an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of an electronic device in an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Fig. 1 is a flowchart of a method for analyzing a linguistic element in an embodiment of the present disclosure, where the embodiment is applicable to a case where a client performs linguistic element analysis, the method may be executed by a linguistic element analysis device, the device may be implemented in a software and/or hardware manner, and the device may be configured in an electronic device, such as a mobile terminal, and specifically includes a mobile phone, a computer, or a tablet computer. Alternatively, the embodiment may be applicable to a case of performing linguistic element analysis in a server, and the method may be performed by a linguistic element analysis apparatus, which may be implemented in software and/or hardware, and may be configured in an electronic device, such as a server.
As shown in fig. 1, the method may specifically include:
s101, obtaining a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes.
In the embodiment of the present disclosure, the preset programming language may be, for example, a C + + programming language. The language element analysis means may store a plurality of source code files in advance, each source code file including a plurality of lines of source code. Alternatively, the linguistic element analysis apparatus may acquire a plurality of source code files, each including a plurality of lines of source code, from other terminals or servers. Specifically, the language element analysis device may analyze multiple lines of source codes in each source code file by using the method described in this embodiment, so as to determine the language elements in each source code file.
And S102, adding a line number in each line of source codes of the plurality of lines of source codes.
For example, a line number is added to each line of source code, for example, the line number may be added at the beginning of each line of source code, or the line number may be added at the end of each line of source code. In addition, the identifier of the line number is not particularly limited in this embodiment.
It is understood that in some other embodiments, the addition of the line number is not limited to the source code file, for example, other information may also be added, and the other information may specifically include information such as processing time of the source code file, a module to which the source code file belongs, a file path of the source code file, and a Message-Digest Algorithm (MD 5), a last modification time (LastModifyTime, LMT), and the like. In the case that the last modification time is not changed, it is indicated that the program source code is not changed, and in this case, the source code file can be accelerated.
S103, identifying preset paragraphs in the multi-line source code added with the line numbers, and replacing the preset paragraphs in the multi-line source code with first preset marks.
For example, the linguistic element analysis apparatus may identify a preset paragraph in the plurality of lines of source code to which the line number is added. Optionally, the preset paragraph includes at least one of: long annotations, short annotations, character strings, native character strings, characters. Specifically, when the linguistic element analysis device identifies a preset paragraph in the multiple lines of source code, the preset paragraph may be replaced with a first preset identifier, for example, the first preset identifier may be denoted as token.
Wherein the long note may specifically be content identified by a symbol such as "/". The short note may specifically be content identified by a symbol such as "//". The character string may be, for example, a combination of symbols such as letters, numbers, and the like. The native string may be, for example, a string preceded by the letter R. The characters may be, for example, letters or the like.
In a case where the linguistic element analysis means identifies a preset paragraph in the plurality of lines of source code to which the line number is added, the preset paragraph in the plurality of lines of source code may be replaced with the first preset flag. For example, the linguistic element analysis device may also replace the String "" Base/algorithmbuffer.h "" with the first preset identification, e.g., [ String-0 ]. After the above-mentioned processing, the plurality of lines of source code correspond to the reforming of the file on an initial basis, and a change in line number may occur during the reforming of the file, for example, lines 4 to 6 in the initial source code become one line, i.e., line 4, after the processing.
It is understood that the one-to-one correspondence between the replaced portion and the replaced portion in the source code may be recorded, and the processed source code may be restored to the source code in the initial state according to the correspondence.
S104, on the basis that the preset paragraphs in the multiple lines of source codes are replaced by the first preset marks, the preset symbols in the multiple lines of source codes are recognized, and the single-line processing is carried out on the part, associated with the preset symbols, of the multiple lines of source codes.
For example, the linguistic element analysis device may further perform a single-line processing on the multiple lines of source code and perform an enhancement processing on a portion of the multiple lines of source code with a weak grammatical feature on the basis of replacing a preset paragraph in the multiple lines of source code with the first preset identifier.
In one possible implementation, identifying a preset symbol in the plurality of lines of source code, and performing unionization processing on a portion of the plurality of lines of source code associated with the preset symbol includes: and identifying a first preset symbol and a second preset symbol which are associated with each other in the plurality of lines of source codes, and adjusting part of the source codes between the first preset symbol and the second preset symbol, the first preset symbol and the second preset symbol to be in the same line.
For example, the first preset symbol may be a left bracket "(" and the second preset symbol may be a right bracket ")". The language element analysis means may identify interrelated left brackets "(" and right brackets ")" in the plurality of lines of source code. Further, the language element analysis means may adjust the part of the source code between the left brackets "(" and right brackets ")", the left brackets "(" and right brackets ")" in the same row. That is, no line feed occurs before the left bracket "(" meets the right bracket ")". For example, assuming that the left brackets "(" and the right brackets in line 38 ")" in line 34 of the source code are interrelated, line 34-line 38 may be adjusted to the same line according to the method in an embodiment of the present disclosure. For example, assuming that lines 34-38 are a function declaration that occupies multiple rows, the function declaration may be made single-threaded by adjusting lines 34-38 to the same row. In addition, the process of singulating annotations is similar to that of function declarations and will not be described herein.
In another possible implementation manner, identifying a preset symbol in the plurality of lines of source code, and performing unionization processing on a portion of the plurality of lines of source code associated with the preset symbol includes: and identifying a keyword in the multi-line source code and a third preset symbol which is closest to the keyword, and adjusting part of the source code between the keyword and the third preset symbol, the keyword and the third preset symbol to be in the same line.
For example, the third preset symbol may be "{". The linguistic element analysis device may identify a keyword in the plurality of lines of source code and the "{" closest to the keyword. For example, the keywords may be enum, class, void, pool, and the like. Taking class as an example, when the linguistic element analysis device identifies the keyword class in the source code and the "{" closest to the keyword class, the part of the source code between the keyword class and the "{" and the keywords class and "{" may be adjusted to be in the same row. If the keywords class and "{" are already in the same row, no adjustment is needed at this time. If in some embodiments, the "{" closest to class is next to class, then the portion of the source code between the keywords class and "{" needs to be aligned to the same row. For example, assuming that line 15 in the source code is a declaration of class, the one-way declaration of class can be achieved by adjusting part of the source code between the keywords class and "{" and the keywords class and "{" in the same line. In addition, the class declaration is not limited to be subjected to single-line processing, for example, the structure and other source codes similar to the structure and the class declaration may also be subjected to single-line processing in a manner similar to the class declaration, and details are not repeated here.
Optionally, the method further includes: and identifying a fourth preset symbol in the plurality of lines of source code, wherein the fourth preset symbol is associated with the third preset symbol, and adding a new line to the next line of the fourth preset symbol. Optionally, a part of the source code between the keyword and the third preset symbol, the content of the same line obtained after the keyword and the third preset symbol are adjusted to be the same as the content of the new line.
For example, the fourth preset symbol may be "}". Since the end point is difficult to recognize by pattern matching due to weak syntactic characteristics, a new line may be added to the next line of "}" to identify the end point, thereby enhancing the characteristics of the end point.
Optionally, the method further includes: and when the keyword is a target keyword, adding a second preset identifier in each line of source codes between the third preset symbol and the fourth preset symbol.
For example, if the enumeration item included in the enumeration enum in a certain line of the source code has weak features, the features of the enumeration item may be enhanced by adding the second preset identifier. For example, the second preset identification may be, for example, a signal. That is, the portion including the asterisk indicates the enumerated item. Specifically, enum may be used as a target keyword, and when the linguistic element analysis device identifies a keyword in the source code and determines that the keyword is the target keyword enum, the "{" and "}" closest to enum may be determined, and an × number is added to each line of the source code between "{" and "}", so as to perform feature enhancement on the enumerated item.
It can be understood that the single-line processing and feature enhancement performed on the source code are not limited to the above-mentioned cases, and may also include other cases, which are not described in detail herein.
S105, determining language elements in the multi-line source code after the single-line processing.
Optionally, determining the language elements in the multiple lines of source code after the single-serialization processing includes: determining language elements in the plurality of lines of source code after the single-line processing through a regular expression.
It is understood that the language elements in the source code are single-lined after the source code is processed through S101-S104, that is, the same language element is in one line, and the same language element is prevented from being distributed in multiple lines. In this case, the regular expressions can be used to match out the language elements in the single-lined source code.
In addition, it is understood that the number of language elements that a line of source code may include may not be limited to one.
Optionally, the language element includes at least one of: notes, classes, variables, enumerations, enumerated terms, functions.
In the present embodiment, the annotations include Runtime type information (RTTI) annotations and User Interface (UI) annotations. The RTTI may specifically refer to a behavior of saving type information of a variable in the C + + source code when the C + + source code runs, and may be used for code automation, such as automatic generation of interface elements, automatic saving of data, and the like. In different programming languages, annotations and RTTI may have different names. For example, RTTI, reflection, run-time type identification, run-time type information are synonyms, which may all refer to RTTI. Java annotation, C # attribute, Qt meta-object, Go tag, Python decorator are similar concepts, which may be collectively referred to as annotations.
An enumerated item may also be referred to as an enumerated subitem. The class comprises a class declaration, the variable comprises a univariate declaration, the function comprises a function declaration, the enumeration comprises an enumeration declaration, and the enumeration comprises an enumeration sub-term declaration. Specifically, an example corresponding to each of the RTTI annotation, UI annotation, class declaration, single variable declaration, function declaration, enumeration declaration, and enumeration sub-item declaration is shown in table 1 below:
TABLE 1
Language element | Examples of the invention |
RTTI notes (e.g., XXX _ RTTI) | XXX_RTTI(name=“foo”) |
UI notes (e.g., XXX _ UI) | XXX_UI(Display=“foo”) |
Class declaration (Class Decl) | class A{ |
Single variable declaration (Single VarDecl) | int a=0; |
Function declaration (FuncDecl) | void foo(); |
Enumeration statement (EnumDecl) | enum A{ |
Enumerate sub-Item declaration (E-Item Decl) | RIGIDBODY_STATIC |
According to the language element analysis method provided by the embodiment of the disclosure, by acquiring the source code file of the preset programming language, a line number is added in each line of source codes of a plurality of lines of source codes included in the source code file, and the line number can be used as auxiliary information to better distinguish each line of source codes. In addition, on the basis, the preset paragraphs in the multi-line source codes are recognized, the preset paragraphs are replaced by the first preset marks, and the influence of the preset paragraphs on the linguistic element analysis can be reduced by replacing the preset paragraphs with the first preset marks because the preset paragraphs are likely to be long and the first preset marks are short. Further, on the basis that the preset paragraphs in the multi-line source code are replaced by the first preset marks, the preset symbols in the multi-line source code are recognized, and single-line processing is performed on the part of the source code associated with the preset symbols, so that the same linguistic element can be distributed in the same line, and the influence on analysis of the linguistic element caused by the fact that the same linguistic element is distributed in multiple lines is avoided. Furthermore, the language elements are identified on the basis of the source codes of multiple lines after single-row processing, so that the method for extracting the language elements from the source codes more accurately is realized.
On the basis of the above embodiment, after determining the language elements in the single-rowed source code, the method further includes the following steps as shown in fig. 2:
s201, replacing the language elements in the multi-line source code after the single-line processing with a third identifier.
For example, after the linguistic element analysis device determines the linguistic elements in the multiple lines of the source code, the linguistic elements in the multiple lines of the source code may be further extracted, and the linguistic elements in the multiple lines of the source code may be replaced with a third identifier, where the third identifier may be token specifically. The language elements such as classes, enumerations, dual morphemes of classes or enumerations, and functions are inclusion bodies (bodies), namely code blocks wrapped by { }, and the rest language elements are single lines. In particular, for functions, the body may be folded into the declaration row.
S202, determining the incidence relation among the language elements according to the third identification.
For example, the language element analysis means may determine an association relationship between the language elements, which includes a CDA relationship and a containment relationship, from the third identification. Where CDA is an english abbreviation for Comment (Comment), declaration (declaration), and Annotation (Annotation). The comments, statements, and annotations may be contiguous during programming, e.g., the top line of a linguistic element statement may be a comment and the bottom line of the linguistic element statement may be an annotation. Additionally, it is to be understood that the top line of a linguistic element declaration may also be unannotated and/or the bottom line of a linguistic element declaration may also be unannotated. In embodiments of the present disclosure, a CDA relationship may be, for example, a relationship between a class of annotations, notes, and notes. In addition, the inclusion relationship in the embodiments of the present disclosure may be, for example, such that "Enum-0" includes "EItem-0" and "EItem-1".
It is understood that the analysis method for the language elements in other source code files is similar to this, and is not described in detail here. When multiple source code files are included in a repository, each source code file in the repository may be traversed and analyzed using the linguistic element analysis method described in embodiments of the present disclosure.
In some embodiments, the method according to embodiments of the present disclosure may further output an intermediate format file, which may include the source code after reformatting and token replacement, for analysis. In addition, the corresponding relation between the language element and the token and the corresponding relation between the preset paragraph and the token can be output.
According to the linguistic element analysis method provided by the embodiment of the disclosure, the linguistic elements in the multi-line source code after single-line processing are replaced by the third identification, and the incidence relation among the linguistic elements is determined according to the third identification, so that the accuracy of analyzing the linguistic elements is further improved.
It is to be understood that after the language element in the C + + source code is analyzed according to the method described in the above embodiment, the language element may be applied in many ways. As shown in fig. 3, the parsing algorithm for extracting annotations may specifically be the linguistic element analysis method described above. The input to the annotated parsing algorithm is annotated C + + source code. The output of the parsing algorithm that can extract annotations is a linguistic element. In some embodiments, an RTTI may also be generated from language elements, which may have a variety of applications, for example, which may be applied in the generation of user interfaces, document generation, code change checking, and the like. In other embodiments, the language elements may also be directly applied in the generation of user interfaces, document generation, code change checking, and the like. The following describes the process of directly applying the language element to the aspects of user interface generation, document generation, code change inspection, etc. by taking the language element as an example.
Optionally, after determining the language elements in the plurality of lines of source code after the single-serialization processing, the method further includes: and generating interface elements in the user interface according to the language elements.
For example, after the language element analyzing device determines the language elements in the plurality of lines of source code, the interface elements in the user interface are further generated according to the language elements. For example, each language element in the C + + source code may correspond to an interface element in the user interface. The interface elements may include, for example, buttons and data presentation areas. The embodiments of the present disclosure do not limit the specific forms of the buttons and the data presentation area in the user interface. The data display area can have various forms. Optionally, the data display area includes at least one of the following: input box, drop-down box, slider, palette, button. Wherein the color palette is used for selection of colors. The buttons may include at least one of a button for function execution, an add-subtract button, wherein the add-subtract button may be used for addition or deletion of an array.
In one possible implementation, generating interface elements in a user interface from the language elements includes: generating a button in the user interface according to a member function of a class associated with an annotation.
For example, a button in the user interface may be generated when the linguistic element analysis device identifies a member function of a class in the C + + source code that is associated with the annotation. When the button is operated, for example, clicked, double-clicked, long-pressed, voice-controlled, gesture-controlled, expression-controlled, etc., the function corresponding to the interface element will be executed.
In another possible implementation, generating an interface element in a user interface according to the language element includes: generating a data presentation region in the user interface from a variable or enumeration associated with an annotation.
For example, a data presentation area in a user interface may be generated when a linguistic element analysis device identifies a variable or enumeration in the C + + source code associated with a comment.
When the linguistic element analysis device identifies an enumeration in the C + + source code associated with the annotation, a drop-down box in the user interface may be generated, and the option in the drop-down box may be specifically generated according to an enumeration item included in the enumeration.
When the linguistic element analysis device identifies a variable associated with the annotation in the C + + source code, a data presentation area corresponding to the type of the variable can be generated according to the type of the variable. For example, when the type of the variable is a character, a character string, a floating point type, the linguistic element analysis means may generate an input box in the user interface, which may be, for example, a text input box, so that the user may set a specific value of the variable in the text input box. When the type of the variable is an integer type, the linguistic element analysis means may generate a slider bar in the user interface, the slider bar may be, for example, a slider bar as shown in fig. 4, the type of the variable Var1 shown in fig. 4 is an integer, the minimum value of the variable Var1 is-9, and the maximum value of the variable Var1 is 9. Accordingly, the minimum and maximum values of the variable Var1 may be set in the C + + source code. The linguistic element analysis device may determine a value corresponding to the vertex at the leftmost end of the slider bar and a value corresponding to the vertex at the rightmost end of the slider bar based on the minimum value and the maximum value of the variable Var 1. For example, the vertex at the leftmost end of the slide bar corresponds to a value of-9, and the vertex at the rightmost end of the slide bar corresponds to a value of 9. Accordingly, the user can edit the specific value of the variable by sliding the slider bar.
Optionally, after determining the language elements in the plurality of lines of source code after the single-serialization processing, the method further includes: a document is automatically generated.
For example, when the linguistic element analysis device identifies a variable or enumeration in the C + + source code associated with the annotation, a document may be automatically generated that may include the content of the class and the enumerated content.
Optionally, the source code file of the preset programming language is a source code file of a first version; after determining the language elements in the single-rowed source code, the method further includes the following steps as shown in fig. 5:
s501, language elements in the source code file of the second version are obtained.
For example, the source code file as described above is a first version of the source code file. Accordingly, the C + + source code in the source code file may be a first version of C + + source code. In particular, the first version may be written by a programmer at a certain time. In some application scenarios, a programmer may also modify the first version of C + + source code at another time to obtain a second version of C + + source code, and the second version of C + + source code may be recorded as source code in the second version of source code file.
In order to check C + + source code changes, for example, API interface changes, the linguistic element analysis device may obtain the source code file of the second version after determining the linguistic elements in the source code file of the first version, and determine the linguistic elements in the source code file of the second version by using the linguistic element analysis method as described above.
S502, comparing the language element in the source code file of the first version with the language element in the source code file of the second version, and determining the difference of the source code file of the first version relative to the source code file of the second version.
For example, the language element analysis device may compare the language elements in the first version of the source code file with the language elements in the second version of the source code file, and determine the difference between the first version of the source code file and the second version of the source code file through the comparison, thereby implementing the cross-version code change check. For example, if the first version is a new version and the second version is an old version, in the case that the source code file of the new version is different from the source code file of the old version, there may be a case of erroneous deletion, that is, a part of the code in the old version may be erroneously deleted in the new version. In this case, by the cross-version code change check described in the embodiment of the present disclosure, the situation of the false deletion can be detected, and an alarm can be issued in advance for the situation of the false deletion, so that the problem of program crash caused by part of the false deletion being unable to be called can be effectively avoided.
In some other embodiments, the linguistic element analysis device may further perform correctness checking on the first version of C + + source code according to the linguistic elements in the first version of source code file, or may perform correctness checking on the second version of C + + source code according to the linguistic elements in the second version of source code file, so as to implement code change checking within the versions.
According to the method for analyzing the language elements, after the language elements in the multi-line source code are determined, the interface elements in the user interface are generated according to the language elements, so that a user can set specific values of variables in the C + + source code through the interface elements, and the flexibility of automatic setting and setting of the variables is improved. In addition, by comparing the language elements in the source code file of the first version with the language elements in the source code file of the second version, the difference of the source code file of the first version relative to the source code file of the second version can be determined, so that the code change check across versions is realized. Since the source code files contain more C + + source codes, if the C + + source codes in the two source code files are directly compared, the code change checking efficiency is low, and in the embodiment, the language elements in the two source code files are extracted to further compare the language elements in the two source code files, so that the code change checking efficiency is greatly improved. In addition, correctness check is performed on the C + + source code of the first version according to the language elements in the source code file of the first version, or correctness check can be performed on the C + + source code of the second version according to the language elements in the source code file of the second version, so that code change check in the versions is realized, and reliability and accuracy of the C + + source code are improved.
FIG. 6 is a flow chart of another method for linguistic element analysis in an embodiment of the present disclosure. As shown in fig. 6, the method of this embodiment is applied to a terminal or a server, and specifically includes:
s601, obtaining a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes.
Specifically, the implementation process of S601 and S101 is consistent with a specific principle, and is not described herein again.
And S602, adding a line number in each line of source codes of the plurality of lines of source codes.
Specifically, the implementation process of S602 and S102 is consistent with specific principles, and is not described herein again.
S603, identifying preset paragraphs in the multi-line source code added with the line numbers, and replacing the preset paragraphs in the multi-line source code with first preset marks.
Specifically, the implementation process of S603 and S103 is consistent with a specific principle, and is not described herein again.
S604, on the basis that the preset paragraphs in the multiple lines of source codes are replaced by the first preset marks, recognizing preset symbols in the multiple lines of source codes, and performing single-line processing on part of the source codes in the multiple lines of source codes, wherein the part of the source codes is associated with the preset symbols.
Specifically, the implementation process of S604 and S104 is consistent with the specific principle, and is not described herein again
S605, determining the annotation in the multi-line source code after the single-line processing and the language element related to the annotation.
For example, the linguistic element analysis means may determine the correlation between the linguistic elements, thereby determining the annotation in the C + + source code and the linguistic element related to the annotation.
And S606, displaying the interface elements corresponding to the language elements in the user interface.
For example, each language element in the C + + source code may correspond to an interface element in the user interface. And when the language element analysis device determines the language elements in the multi-line source code, generating interface elements in the user interface according to the language elements.
For example, a button in the user interface may be generated when the linguistic element analysis device identifies a member function of a class in the C + + source code that is associated with the annotation. When the linguistic element analysis device identifies a variable or enumeration in the C + + source code associated with the annotation, a data presentation area in the user interface may be generated.
When the linguistic element analysis device identifies an enumeration in the C + + source code associated with the annotation, a drop-down box in the user interface may be generated, and the option in the drop-down box may be specifically generated according to an enumeration item included in the enumeration.
When the linguistic element analysis device identifies a variable associated with the annotation in the C + + source code, a data presentation area corresponding to the type of the variable can be generated according to the type of the variable. For example, when the type of the variable is a character, a character string, a floating point type, the linguistic element analysis means may generate an input box in the user interface, which may be, for example, a text input box, so that the user may set a specific value of the variable in the text input box. When the type of the variable is an integer type, the linguistic element analysis means may generate a slider bar in the user interface, the slider bar may be, for example, a slider bar as shown in fig. 4, the type of the variable Var1 shown in fig. 4 is an integer, the minimum value of the variable Var1 is-9, and the maximum value of the variable Var1 is 9. Accordingly, the minimum and maximum values of the variable Var1 may be set in the C + + source code. The linguistic element analysis device may determine a value corresponding to the vertex at the leftmost end of the slider bar and a value corresponding to the vertex at the rightmost end of the slider bar based on the minimum value and the maximum value of the variable Var 1. For example, the vertex at the leftmost end of the slide bar corresponds to a value of-9, and the vertex at the rightmost end of the slide bar corresponds to a value of 9. Accordingly, the user can edit the specific value of the variable by sliding the slider bar.
According to the language element analysis method provided by the embodiment of the disclosure, by acquiring the source code file of the preset programming language, a line number is added in each line of source codes of a plurality of lines of source codes included in the source code file, and the line number can be used as auxiliary information to better distinguish each line of source codes. In addition, on the basis, the preset paragraphs in the multi-line source codes are recognized, the preset paragraphs are replaced by the first preset marks, and the influence of the preset paragraphs on the linguistic element analysis can be reduced by replacing the preset paragraphs with the first preset marks because the preset paragraphs are possibly relatively long and the first preset marks are relatively short. Further, on the basis that the preset paragraphs in the multi-line source code are replaced by the first preset marks, the preset symbols in the multi-line source code are recognized, and single-line processing is performed on the part of the source code associated with the preset symbols, so that the same linguistic element can be distributed in the same line, and the influence on analysis of the linguistic element caused by the fact that the same linguistic element is distributed in multiple lines is avoided. Furthermore, the language elements are identified on the basis of the source codes of multiple lines after single-row processing, so that the method for extracting the language elements from the source codes more accurately is realized. In addition, after the language elements in the multi-line source code are determined, the interface elements in the user interface are generated according to the language elements, so that a user can set specific values of variables in the C + + source code through the interface elements, and the flexibility of automatic setting and setting of the variables is improved.
Fig. 7 is a schematic structural diagram of a linguistic element analysis device in an embodiment of the present disclosure. The linguistic element analysis apparatus provided in the embodiment of the present disclosure may be configured in a client, or may be configured in a server, where the linguistic element analysis apparatus 70 specifically includes:
an obtaining module 71, configured to obtain a source code file of a preset programming language, where the source code file includes multiple lines of source codes;
a line number adding module 72, configured to add a line number in each line of the source codes of the plurality of lines of source codes;
an identifying module 73, configured to identify a preset paragraph in the plurality of lines of source code to which the line number is added;
a replacing module 74, configured to replace a preset paragraph in the plurality of lines of source code with a first preset identifier;
the identification module 73 is further configured to: on the basis that the replacement module 74 replaces the preset paragraph in the plurality of lines of source code with the first preset identifier, recognizing a preset symbol in the plurality of lines of source code;
a processing module 75, configured to perform unionization processing on a portion of the source code associated with the preset symbol in the plurality of lines of source code;
a determining module 76 for determining the language elements in the plurality of lines of source code after the single-line processing.
Optionally, the identifying module 73 is specifically configured to: identifying a first preset symbol and a second preset symbol associated with each other in the plurality of lines of source code, where the processing module 75 is specifically configured to: and adjusting part of source codes between the first preset symbol and the second preset symbol, the first preset symbol and the second preset symbol in the same row.
Optionally, the identifying module 73 is specifically configured to: identifying a keyword in the plurality of lines of source code and a third preset symbol closest to the keyword, where the processing module 75 is specifically configured to: and adjusting part of the source codes between the keywords and the third preset symbols, and the keywords and the third preset symbols on the same line.
Optionally, the identification module 73 is further configured to: identifying a fourth preset symbol in the plurality of lines of source code associated with the third preset symbol, the processing module 75 being further configured to: and adding a new row to the next row of the fourth preset symbol.
Optionally, a part of the source code between the keyword and the third preset symbol, the content of the same line obtained after the keyword and the third preset symbol are adjusted to be the same as the content of the new line.
Optionally, the processing module 75 is further configured to: and when the keyword is a target keyword, adding a second preset identifier in each line of source codes between the third preset symbol and the fourth preset symbol.
Optionally, the determining module 76 is specifically configured to: determining language elements in the plurality of lines of source code after the single-line processing through a regular expression.
Optionally, the processing module 75 is further configured to: after determining module 76 determines linguistic elements in the single-lined plurality of lines of source code, replacing the linguistic elements in the single-lined plurality of lines of source code with a third identification; the determination module 76 is further configured to: and determining the incidence relation between the language elements according to the third identification.
Optionally, the preset paragraph includes at least one of:
long annotations, short annotations, character strings, native character strings, characters.
Optionally, the language element includes at least one of:
notes, classes, variables, enumerations, enumerated terms, functions.
Optionally, the language element analyzing apparatus 70 further includes: a generating module 77, configured to generate an interface element in the user interface according to the language element after the determining module 76 determines the language element in the multiple lines of source code after the single-serialization processing.
Optionally, the generating module 77 is specifically configured to: generating a button in the user interface according to a member function of a class associated with an annotation.
Optionally, the generating module 77 is specifically configured to: generating a data presentation region in the user interface according to a variable or enumeration associated with an annotation.
Optionally, the data display area includes at least one of the following:
input box, drop-down box, slider, palette, button.
Optionally, the source code file of the preset programming language is a source code file of a first version; the obtaining module 71 is further configured to: after determining the language elements in the plurality of lines of source code after the single-line processing, the determining module 76 obtains the language elements in the source code file of the second version; the determination module 76 is further configured to: determining differences in the first version of the source code file relative to the second version of the source code file by comparing language elements in the first version of the source code file and language elements in the second version of the source code file.
The apparatus for analyzing a linguistic element provided in the embodiment of the disclosure may perform steps performed by a client or a server in the method for analyzing a linguistic element provided in the embodiment of the disclosure, and the steps and the advantages of the apparatus for analyzing a linguistic element are not described herein again.
Fig. 8 is a schematic structural diagram of a linguistic element analysis device in an embodiment of the present disclosure. The linguistic element analysis apparatus provided in the embodiment of the present disclosure may be configured in the client, or may be configured in the server, and the linguistic element analysis apparatus 80 specifically includes:
an obtaining module 81, configured to obtain a source code file of a preset programming language, where the source code file includes multiple lines of source codes;
a line number adding module 82, configured to add a line number in each line of the source codes of the plurality of lines of source codes;
an identifying module 83, configured to identify a preset paragraph in the plurality of lines of source code to which the line number is added;
a replacing module 84, configured to replace a preset paragraph in the plurality of lines of source code with a first preset identifier;
the identification module 83 is further configured to: on the basis that the replacement module 84 replaces the preset paragraph in the plurality of lines of source code with the first preset identifier, recognizing a preset symbol in the plurality of lines of source code;
a processing module 85, configured to perform unionization processing on a part of the multiple lines of source codes that is associated with the preset symbol;
a determining module 86 for determining annotations in the plurality of lines of source code after the single-serialization processing and language elements related to the annotations;
and the display module 87 is used for displaying the interface elements corresponding to the language elements in the user interface.
The apparatus for analyzing a linguistic element provided in the embodiment of the disclosure may perform steps performed by a client or a server in the method for analyzing a linguistic element provided in the embodiment of the disclosure, and the steps and the advantages of the apparatus for analyzing a linguistic element are not described herein again.
Fig. 9 is a schematic structural diagram of an electronic device in an embodiment of the present disclosure. Referring now specifically to fig. 9, a schematic diagram of an electronic device 900 suitable for use in implementing embodiments of the present disclosure is shown. The electronic device 900 in the disclosed embodiments may include, but is not limited to, mobile terminals such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle-mounted terminal (e.g., a car navigation terminal), and the like, and fixed terminals such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 9, the electronic device 900 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 901 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage means 908 into a Random Access Memory (RAM) 903. In the RAM903, various programs and data necessary for the operation of the electronic apparatus 900 are also stored. The processing apparatus 901, ROM 902, and RAM903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
Generally, the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 907 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 908 including, for example, magnetic tape, hard disk, etc.; and a communication device 909. The communication device 909 may allow the electronic apparatus 900 to perform wireless or wired communication with other apparatuses to exchange data. While fig. 9 illustrates an electronic device 900 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device 909, or installed from the storage device 908, or installed from the ROM 902. The computer program performs the above-described functions defined in the methods of the embodiments of the present disclosure when executed by the processing apparatus 901.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining language elements in the plurality of lines of source code after the single-serialization processing.
Optionally, the electronic device may also perform other steps as described in the above embodiments.
Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining annotations in the plurality of lines of source code after the single serialization processing and language elements related to the annotations;
and displaying an interface element corresponding to the language element in a user interface.
Optionally, the electronic device may also perform other steps as described in the above embodiments.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to one or more embodiments of the present disclosure, there is provided a linguistic element analysis method, including:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining language elements in the plurality of lines of source code after the single-serialization processing.
According to one or more embodiments of the present disclosure, in a linguistic element analysis method provided by the present disclosure, recognizing a preset symbol in a plurality of lines of source code, and performing unionization processing on a part of the source code associated with the preset symbol in the plurality of lines of source code, includes:
and identifying a first preset symbol and a second preset symbol which are associated with each other in the plurality of lines of source codes, and adjusting part of the source codes between the first preset symbol and the second preset symbol, the first preset symbol and the second preset symbol to be in the same line.
According to one or more embodiments of the present disclosure, in a linguistic element analysis method provided by the present disclosure, recognizing a preset symbol in a plurality of lines of source code, and performing unionization processing on a part of the source code associated with the preset symbol in the plurality of lines of source code, includes:
and identifying a keyword in the multi-line source code and a third preset symbol which is closest to the keyword, and adjusting part of the source code between the keyword and the third preset symbol, the keyword and the third preset symbol to be in the same line.
According to one or more embodiments of the present disclosure, in the linguistic element analysis method provided by the present disclosure, the method further includes:
and identifying a fourth preset symbol in the plurality of lines of source code, wherein the fourth preset symbol is associated with the third preset symbol, and adding a new line to the next line of the fourth preset symbol.
According to one or more embodiments of the present disclosure, in the linguistic element analysis method provided by the present disclosure, the partial source code between the keyword and the third preset symbol, the keyword and the third preset symbol adjust that the content of the same line obtained after the same line is the same as the content of the new line.
According to one or more embodiments of the present disclosure, in the linguistic element analysis method provided by the present disclosure, the method further includes:
and when the keyword is a target keyword, adding a second preset identifier in each line of source codes between the third preset symbol and the fourth preset symbol.
According to one or more embodiments of the present disclosure, in a method for analyzing linguistic elements provided by the present disclosure, determining linguistic elements in the plurality of lines of source code after the single-serialization processing includes:
determining language elements in the plurality of lines of source code after the single-line processing through a regular expression.
According to one or more embodiments of the present disclosure, in the method for analyzing linguistic elements provided by the present disclosure, after determining linguistic elements in the plurality of lines of source code after the single-serialization processing, the method further includes:
replacing language elements in the plurality of lines of source code after the single-line processing with a third identifier;
and determining the incidence relation between the language elements according to the third identification.
According to one or more embodiments of the present disclosure, in the method for analyzing a linguistic element provided by the present disclosure, the preset paragraph includes at least one of:
long annotations, short annotations, character strings, native character strings, characters.
According to one or more embodiments of the present disclosure, in the method for analyzing linguistic elements provided by the present disclosure, the linguistic elements include at least one of:
notes, classes, variables, enumerations, enumerated terms, functions.
According to one or more embodiments of the present disclosure, in the method for analyzing linguistic elements provided by the present disclosure, after determining linguistic elements in the plurality of lines of source code after the single-serialization processing, the method further includes:
and generating interface elements in the user interface according to the language elements.
According to one or more embodiments of the present disclosure, in a method for analyzing a linguistic element provided by the present disclosure, generating an interface element in a user interface according to the linguistic element includes:
generating a button in the user interface according to a member function of a class associated with an annotation.
According to one or more embodiments of the present disclosure, in a method for analyzing a linguistic element provided by the present disclosure, generating an interface element in a user interface according to the linguistic element includes:
generating a data presentation region in the user interface from a variable or enumeration associated with an annotation.
According to one or more embodiments of the present disclosure, in the linguistic element analysis method provided by the present disclosure, the data presentation area includes at least one of:
input box, drop-down box, slider, palette, button.
According to one or more embodiments of the present disclosure, in the method for analyzing a language element provided by the present disclosure, the source code file of the preset programming language is a first version of the source code file;
after determining the language elements in the plurality of lines of source code after the single-serialization processing, the method further comprises:
acquiring language elements in the source code file of the second version;
determining differences in the first version of the source code file relative to the second version of the source code file by comparing language elements in the first version of the source code file and language elements in the second version of the source code file.
According to one or more embodiments of the present disclosure, there is provided a linguistic element analysis method, including:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining annotations in the plurality of lines of source code after the single serialization processing and language elements related to the annotations;
and displaying the interface element corresponding to the language element in the user interface.
According to one or more embodiments of the present disclosure, there is provided a linguistic element analysis apparatus including:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a source code file of a preset programming language, and the source code file comprises a plurality of lines of source codes;
the line number adding module is used for adding a line number in each line of source codes of the plurality of lines of source codes;
the identification module is used for identifying a preset paragraph in the multi-line source code added with the line number;
the replacing module is used for replacing a preset paragraph in the multi-line source code with a first preset identifier;
the identification module is further configured to: on the basis that a replacement module replaces preset paragraphs in the multi-line source code with the first preset identification, recognizing preset symbols in the multi-line source code;
the processing module is used for performing single-line processing on part of the source codes associated with the preset symbols in the multiple lines of source codes;
a determining module for determining the language elements in the plurality of lines of source code after the single-line processing.
According to one or more embodiments of the present disclosure, in the linguistic element analysis apparatus provided by the present disclosure, the recognition module is specifically configured to: identifying a first preset symbol and a second preset symbol which are associated with each other in the plurality of lines of source codes, wherein the processing module is specifically configured to: and adjusting part of source codes between the first preset symbol and the second preset symbol, the first preset symbol and the second preset symbol in the same row.
According to one or more embodiments of the present disclosure, in the linguistic element analysis apparatus provided by the present disclosure, the recognition module is specifically configured to: identifying a keyword in the multi-line source code and a third preset symbol closest to the keyword, wherein the processing module is specifically configured to: and adjusting part of the source codes between the keywords and the third preset symbols, and the keywords and the third preset symbols on the same line.
According to one or more embodiments of the present disclosure, in the linguistic element analysis device provided by the present disclosure, the recognition module is further configured to: identifying a fourth pre-set symbol of the plurality of lines of source code associated with the third pre-set symbol, the processing module further to: and adding a new row to the next row of the fourth preset symbol.
According to one or more embodiments of the present disclosure, in the linguistic element analysis apparatus provided by the present disclosure, the partial source code between the keyword and the third preset symbol, the keyword and the third preset symbol adjust that the content of the same line obtained after the same line is the same as the content of the new line.
According to one or more embodiments of the present disclosure, in the linguistic element analysis device provided by the present disclosure, the processing module is further configured to: and when the keyword is a target keyword, adding a second preset identifier in each line of source codes between the third preset symbol and the fourth preset symbol.
According to one or more embodiments of the present disclosure, in the linguistic element analysis apparatus provided by the present disclosure, the determination module is specifically configured to: determining language elements in the plurality of lines of source code after the single-line processing through a regular expression.
According to one or more embodiments of the present disclosure, in the linguistic element analysis device provided by the present disclosure, the processing module is further configured to: replacing, after a determination module determines linguistic elements in the single-lined plurality of lines of source code, the linguistic elements in the single-lined plurality of lines of source code with a third identification; the determination module is further configured to: and determining the incidence relation between the language elements according to the third identification.
According to one or more embodiments of the present disclosure, in the linguistic element analysis apparatus provided by the present disclosure, the preset paragraph includes at least one of:
long annotations, short annotations, character strings, native character strings, characters.
According to one or more embodiments of the present disclosure, in a linguistic element analysis apparatus provided by the present disclosure, the linguistic element includes at least one of:
notes, classes, variables, enumerations, enumerated terms, functions.
According to one or more embodiments of the present disclosure, in a linguistic element analysis apparatus provided by the present disclosure, the linguistic element analysis apparatus further includes: and the generating module is used for generating interface elements in a user interface according to the language elements after the determining module determines the language elements in the plurality of lines of source codes after the single-line processing.
According to one or more embodiments of the present disclosure, in the linguistic element analysis device provided in the present disclosure, the generation module is specifically configured to: generating a button in the user interface according to a member function of a class associated with an annotation.
According to one or more embodiments of the present disclosure, in the linguistic element analysis device provided in the present disclosure, the generation module is specifically configured to: generating a data presentation region in the user interface according to a variable or enumeration associated with an annotation.
According to one or more embodiments of the present disclosure, in the linguistic element analysis device provided by the present disclosure, the data presentation area includes at least one of:
input box, drop-down box, slider, palette, button.
According to one or more embodiments of the present disclosure, in a linguistic element analysis apparatus provided by the present disclosure, the source code file of the preset programming language is a first version of the source code file; the acquisition module is further configured to: after the determining module determines the language elements in the plurality of lines of source codes after the single-line processing, the language elements in the source code file of the second version are obtained; the determination module is further configured to: determining differences in the first version of the source code file relative to the second version of the source code file by comparing language elements in the first version of the source code file and language elements in the second version of the source code file.
According to one or more embodiments of the present disclosure, there is provided a linguistic element analysis apparatus including:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a source code file of a preset programming language, and the source code file comprises a plurality of lines of source codes;
the line number adding module is used for adding a line number in each line of source codes of the plurality of lines of source codes;
the identification module is used for identifying a preset paragraph in the multi-line source code added with the line number;
the replacing module is used for replacing a preset paragraph in the multi-line source code with a first preset identifier;
the identification module is further configured to: on the basis that a replacement module replaces preset paragraphs in the multi-line source code with the first preset identification, recognizing preset symbols in the multi-line source code;
the processing module is used for performing single-line processing on part of the source codes associated with the preset symbols in the multiple lines of source codes;
a determining module, configured to determine an annotation in the plurality of lines of source code after the single-serialization processing and a language element related to the annotation;
and the display module is used for displaying the interface elements corresponding to the language elements in the user interface.
In accordance with one or more embodiments of the present disclosure, there is provided an electronic device including:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement any of the linguistic element analysis methods provided by the disclosure.
According to one or more embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a linguistic element analysis method as any one of provided by the present disclosure.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (20)
1. A method of linguistic element analysis, the method comprising:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is recognized, and single-line processing is carried out on part of the multiple lines of source codes, which are associated with the preset symbol;
determining language elements in the plurality of lines of source code after the single-serialization processing.
2. The method of claim 1, wherein identifying a predetermined symbol in the plurality of lines of source code and uniserifying a portion of source code in the plurality of lines of source code associated with the predetermined symbol comprises:
and identifying a first preset symbol and a second preset symbol which are associated with each other in the plurality of lines of source codes, and adjusting part of the source codes between the first preset symbol and the second preset symbol, the first preset symbol and the second preset symbol to be in the same line.
3. The method of claim 1, wherein identifying a predetermined symbol in the plurality of lines of source code and uniserifying a portion of source code in the plurality of lines of source code associated with the predetermined symbol comprises:
and identifying a keyword in the multi-line source code and a third preset symbol which is closest to the keyword, and adjusting part of the source code between the keyword and the third preset symbol, the keyword and the third preset symbol to be in the same line.
4. The method of claim 3, further comprising:
and identifying a fourth preset symbol in the plurality of lines of source code, wherein the fourth preset symbol is associated with the third preset symbol, and adding a new line to the next line of the fourth preset symbol.
5. The method according to claim 4, wherein the part of the source code between the keyword and the third predetermined symbol, the keyword and the third predetermined symbol adjust the content of the same line obtained after the same line to be the same as the content of the new line.
6. The method of claim 4, further comprising:
and when the keyword is a target keyword, adding a second preset identifier in each line of source codes between the third preset symbol and the fourth preset symbol.
7. The method of claim 1, wherein determining the linguistic elements in the plurality of lines of source code after the single-serialization processing comprises:
determining language elements in the plurality of lines of source code after the single-line processing through a regular expression.
8. The method of claim 1, wherein after determining the single-rowed language elements in the plurality of lines of source code, the method further comprises:
replacing language elements in the plurality of lines of source code after the single-line processing with a third identifier;
and determining the incidence relation between the language elements according to the third identification.
9. The method of any one of claims 1-8, wherein the predetermined paragraph comprises at least one of:
long annotations, short annotations, character strings, native character strings, characters.
10. The method of any of claims 1-8, wherein the linguistic elements include at least one of:
notes, classes, variables, enumerations, enumerated terms, functions.
11. The method of claim 1, wherein after determining the single-rowed language elements in the plurality of lines of source code, the method further comprises:
and generating interface elements in the user interface according to the language elements.
12. The method of claim 11, wherein generating interface elements in a user interface from the language elements comprises:
generating a button in the user interface according to a member function of a class associated with an annotation.
13. The method of claim 11, wherein generating interface elements in a user interface from the language elements comprises:
generating a data presentation region in the user interface from a variable or enumeration associated with an annotation.
14. The method of claim 13, wherein the data presentation area comprises at least one of:
input box, drop-down box, slider, palette, button.
15. The method of claim 1, wherein the source code file of the predetermined programming language is a first version of the source code file;
after determining the language elements in the plurality of lines of source code after the single-serialization processing, the method further comprises:
acquiring language elements in the source code file of the second version;
determining differences in the first version of the source code file relative to the second version of the source code file by comparing language elements in the first version of the source code file and language elements in the second version of the source code file.
16. A method of linguistic element analysis, the method comprising:
acquiring a source code file of a preset programming language, wherein the source code file comprises a plurality of lines of source codes;
adding a line number in each line of source code of the plurality of lines of source code;
identifying a preset paragraph in the plurality of lines of source code added with the line number, and replacing the preset paragraph in the plurality of lines of source code with a first preset identifier;
on the basis that a preset paragraph in the multiple lines of source codes is replaced by the first preset identification, a preset symbol in the multiple lines of source codes is identified, and single-line processing is carried out on part of the multiple lines of source codes, which is associated with the preset symbol;
determining annotations in the plurality of lines of source code after the single serialization processing and language elements related to the annotations;
and displaying the interface element corresponding to the language element in the user interface.
17. A language element analysis device, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a source code file of a preset programming language, and the source code file comprises a plurality of lines of source codes;
the line number adding module is used for adding a line number in each line of source codes of the plurality of lines of source codes;
the identification module is used for identifying a preset paragraph in the multi-line source code added with the line number;
the replacing module is used for replacing a preset paragraph in the multi-line source code with a first preset identifier;
the identification module is further configured to: on the basis that the replacement module replaces preset paragraphs in the multiple lines of source codes with the first preset identifications, recognizing preset symbols in the multiple lines of source codes;
the processing module is used for performing single-line processing on part of the source codes associated with the preset symbols in the multiple lines of source codes;
a determining module for determining the language elements in the plurality of lines of source code after the single-line processing.
18. A language element analysis device, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a source code file of a preset programming language, and the source code file comprises a plurality of lines of source codes;
the line number adding module is used for adding a line number in each line of source codes of the plurality of lines of source codes;
the identification module is used for identifying a preset paragraph in the multi-line source code added with the line number;
the replacing module is used for replacing a preset paragraph in the multi-line source code with a first preset identifier;
the identification module is further configured to: on the basis that the replacement module replaces preset paragraphs in the multiple lines of source codes with the first preset identifications, recognizing preset symbols in the multiple lines of source codes;
the processing module is used for performing single-line processing on part of the source codes associated with the preset symbols in the multiple lines of source codes;
a determining module, configured to determine an annotation in the plurality of lines of source code after the single-serialization processing and a language element related to the annotation;
and the display module is used for displaying the interface elements corresponding to the language elements in the user interface.
19. An electronic device, characterized in that the electronic device comprises:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-16.
20. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-16.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011190547.4A CN114443128A (en) | 2020-10-30 | 2020-10-30 | Language element analysis method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011190547.4A CN114443128A (en) | 2020-10-30 | 2020-10-30 | Language element analysis method and device, electronic equipment and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN114443128A true CN114443128A (en) | 2022-05-06 |
Family
ID=81357982
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202011190547.4A Pending CN114443128A (en) | 2020-10-30 | 2020-10-30 | Language element analysis method and device, electronic equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114443128A (en) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020007483A1 (en) * | 1997-01-29 | 2002-01-17 | Lopez Luis R. | Interactive flow visualization, graphical editing and analysis of textual languages |
US6463578B1 (en) * | 1999-11-23 | 2002-10-08 | International Business Machines Corporation | Systems, methods and computer program products for debugging java server page files using compiled java class file modifications |
US6993710B1 (en) * | 1999-10-05 | 2006-01-31 | Borland Software Corporation | Method and system for displaying changes of source code |
CN103927212A (en) * | 2013-01-11 | 2014-07-16 | 腾讯科技(深圳)有限公司 | Method and device for automatically analyzing source file information |
CN106919434A (en) * | 2017-03-22 | 2017-07-04 | 恒生电子股份有限公司 | A kind of code generating method and device |
CN111767055A (en) * | 2020-06-16 | 2020-10-13 | 合肥本源量子计算科技有限责任公司 | Quantum program compiling method and device |
-
2020
- 2020-10-30 CN CN202011190547.4A patent/CN114443128A/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020007483A1 (en) * | 1997-01-29 | 2002-01-17 | Lopez Luis R. | Interactive flow visualization, graphical editing and analysis of textual languages |
US6993710B1 (en) * | 1999-10-05 | 2006-01-31 | Borland Software Corporation | Method and system for displaying changes of source code |
US6463578B1 (en) * | 1999-11-23 | 2002-10-08 | International Business Machines Corporation | Systems, methods and computer program products for debugging java server page files using compiled java class file modifications |
CN103927212A (en) * | 2013-01-11 | 2014-07-16 | 腾讯科技(深圳)有限公司 | Method and device for automatically analyzing source file information |
CN106919434A (en) * | 2017-03-22 | 2017-07-04 | 恒生电子股份有限公司 | A kind of code generating method and device |
CN111767055A (en) * | 2020-06-16 | 2020-10-13 | 合肥本源量子计算科技有限责任公司 | Quantum program compiling method and device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111274760B (en) | Rich text data processing method and device, electronic equipment and computer storage medium | |
CN112015430B (en) | JavaScript code translation method, device, computer equipment and storage medium | |
CN111736840B (en) | Method for compiling applet application, method for running applet application, storage medium and electronic device | |
US10353702B2 (en) | Source code element signatures | |
US9477651B2 (en) | Finding partition boundaries for parallel processing of markup language documents | |
CN110780874B (en) | Method and device for generating information | |
CN113760729A (en) | Code detection method and device | |
US20150161160A1 (en) | Application Localization | |
CN112783482A (en) | Visual form generation method, device, equipment and storage medium | |
CN111984262A (en) | WeChat cascading style sheet file processing method, device, equipment and storage medium | |
US20230129159A1 (en) | Method, device and computer program product for application testing | |
CN111124541A (en) | Configuration file generation method, device, equipment and medium | |
US11687735B2 (en) | Method, apparatus, device and storage medium for outputting information | |
US20180314683A1 (en) | Method and device for processing natural language | |
CN113177421A (en) | Method, device, equipment and storage medium for quality inspection of translation document | |
CN111367791B (en) | Method, device, medium and electronic equipment for generating test case | |
CN114443128A (en) | Language element analysis method and device, electronic equipment and storage medium | |
CN113268617A (en) | Method and device for detecting metadata of papers | |
CN113138767A (en) | Code language conversion method, device, electronic equipment and storage medium | |
CN109725932B (en) | Method and device for generating description document of application component | |
CN113761906A (en) | Method, device, equipment and computer readable medium for analyzing document | |
CN114492413B (en) | Text proofreading method and device and electronic equipment | |
CN110796137A (en) | Method and device for identifying image | |
CN110471667A (en) | A kind of method, apparatus, medium and electronic equipment for auditing source program | |
CN111209348B (en) | Method and device for outputting information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |