Diagram language for computer programming

• US 9,575,731 B1
• Filed: 06/22/2015
• Issued: 02/21/2017
• Est. Priority Date: 06/22/2015
• Status: Expired due to Fees

• Current Assignee: Chaorong Peng
• Original Assignee: Chaorong Peng
• Inventors: Peng, Chaorong
• Primary Examiner(s): Dorais, Craig
• Application Number:
  US14/745,817
• Time in Patent Office: 610 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/51 Source to source

Abstract

Embodiments of the present invention is Diagram Language (DL) that uses models as diagrams to represent Keyword Structure Definition (KSD) or Function Structure Definition (FSD) that are used in tradition High Level Language (HLL) such as C++; The diagrams are parallel and distribution formation to indicate that KSD or FSD relationship in diagrams; Diagram-to-diagram, diagram-to-text and text-to-diagram in 3D that transformation are used on typically analyzed to find out properties of the diagrams subject, or transformation to constructor other types of diagrams in the DL; The object with specify characters is to be freely random walk in database; Compile programming recognize diagram information with DL-code to process program; The DL is used on the general HLL that can be implemented to allow DL and another software programs communication with each other.

Claims

1. A Diagram Language (DL) for computer programming, comprising:

at least one function performing mathematical calculations, string manipulations, character manipulations, input operations, output operations, error checking and other related support computing operations;

wherein the at least one function provides a group of capabilities comprising;

at least one structure definition allowing a programmer to modularize a program;

at least one ID (identifier) representing location of an object in a structure definition;

at least one member representing a variable that is associated with the structure definition;

at least one Member_Function representing a function of the at least one function that is associated with a structure definition of said at least one structure definition;

at least one Member-diagram indicating the at least one member inserted into the at least one member-diagram, thereby creating a Member-diagram, comprising at least one diagram comprising Members that are into the at least one diagram;

at least one extension .k representing a structure definition;

at least one extension .dl indicating a code in a file written with the DL;

at least one type_name.k representing a programming-defined object type from an object oriented programming language;

at least one DL-type_name-diagram representing a declaration statement of the structure definition;

creating the DL-typename-diagram comprises the steps of;

creating a diagram in which the type name.k is placed within it;

in instances when the Member-diagram is attached to the DL-type_name-diagram indicating that the members are of the type name.k;

at least one Access Specific representing access Members;

at least one DL-type_name.k.dl file wherein, the FileName of the DL-type_name.k.dl comprises a type name.k and an extension .dl and provides a user-definition structure statement in the DL, wherein the DL-type_name.k.dl maintains only a first DL-type_name-diagram and the Member-diagram if the Member-diagram is attached to DL-type_name-diagram;

at least one DL-KSD diagram representing the DL-type_name.k.dl and creating a DL-KSD diagram comprising the step of;

creating a diagram, wherein the type name.k is placed into said diagram;

wherein k has a linking that connects with the DL-type_name.k.dl file;

at least one object representing a variable in the structure definition;

at least one DL-object comprising its own ID;

at least one DL-type representing a structure type that is used to declare variables and declare a DL-object statement, comprising;

a DL-type and a DL-object;

at least one typeUnderline representing the DL-type;

at least one object, wherein said object is for accessible Members in order to access an Access Specific field and wherein the object comprises another object comprising a typeUnderline;

at least one FunctionArgument representing an argument in the Function, wherein the FunctionArgument comprises the DL-type and a DL-object pair;

at least a DL-typeList that comprises at least one DL-type;

at least one FunctionID representing a Function'"'"'s individuality in the programming, wherein the FunctionID comprises a return-value-type;

function-name(DL-typeList);

at least one underline representing a connection to the File;

at least one FunctionTile representing the Function'"'"'s individuality in the DL-type_name.k.dl file and the FunctionTile comprises an underline;

at least one Beginning-diagram representing a step to start to process the Function programming, wherein the FunctionTile comprising the underline is placed into the at least one Beginning-diagram;

at least one processing-diagram representing the step to continue processing a next diagram if any next diagram exists;

at least one Body-diagram representing a function statement, wherein the Function statement is inserted into the processing-diagram;

at least one End-diagram representing the step to End processing of the Function programming;

at least one GlobalList representing public information, wherein a GlobalList of the at least one GlobalList comprises a declaration statement that comprises the DL-type, the DL-object and the FunctionTile comprising an underline;

at least one FunctionID.dl file representing Function structure information, wherein the FunctionID.dl file comprises;

the at least one Beginning-diagram, the at least one processing-diagram and the at least one End-diagram;

at least one fromModel representing the Object in the DL-KSD, that can access the Members in the Member-diagram of another DL-KSD;

at least one toModel representing the Members in the DL-KSD that are accessed by the Object that comprises at least one individual fromModel from said at least one fromModel;

at least one Access-diagram representing a step to access Members from one DL-KSD from the Member-diagram of another DL-KSD;

at least one Perpendicular-diagram representing a variable that belongs to the part of the DL-KSD.

2. The Diagram Language (DL) for computer programming claim 1, wherein the Access Specific field represents the Members are public.

3. The Diagram Language (DL) for computer programming claim 1, wherein the Access Specific field represents the Members are private.

4. The Diagram Language (DL) for computer programming claim 1, wherein the Access Specific field represents the Members are protected.

5. The Diagram Language (DL) for computer programming in claim 1 wherein a FunctionTile with an underline that links to said DL-type_name.k.dl file.

6. The Diagram Language (DL) for computer programming in claim 1, wherein the End-diagram represents a End of Function programming without a return value.

7. The Diagram Language (DL) for computer programming in claim 1, wherein the End-diagram represents an End of Function programming with a return value.

8. The Diagram Language (DL) for computer programming in claim 1, wherein the Access-diagram comprises a diagram connection with one fromModel and one toModel, wherein the fromModel is attached to a middle of the DL-KSD and the toModel is attached to the Member-diagram of another DL-KSD in order to access the Access-Specific field.

9. The Diagram Language (DL) for computer programming claim 1, wherein the object comprises the location of said DL-type_name.k.dl file.

10. The Diagram Language (DL) for computer programming claim 1, wherein the object comprises the location of said GlobalList file.

11. The Diagram Language (DL) for computer programming claim 1, wherein the object comprises the location of said FunctionID file.