Command script parsing using local and extended storage for command lookup
First Claim
1. A computerized method for parsing and verifying the contents of a command script submitted for execution, comprising the steps of:
- providing a command script including at least one token and written in a scripting language;
providing a first, substantially rapidly-accessible data store containing at least one primary function signature definition including a primary function name that is associated with an operational command that does not require data retrieval for completion, and a primary parameter list associated with the primary function name and having zero or more parameter specifications;
providing a second data store that is less substantially rapidly-accessible than the first data store, the second data store containing at least one secondary function signature definition including a secondary function name that is associated with a command that requires data retrieval for completion, and a secondary parameter list associated with the secondary function name and having zero or more parameter specifications;
recognizing at least one portion of the at least one token to potentially represent a reference to a previously defined function in the scripting language, the potential function reference having a potential function name and zero or more potential parameters associated therewith;
searching the first data store for a matching primary function signature definition having a primary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the primary parameter list associated with the same primary function signature definition; and
searching the second data store for a matching secondary function signature definition having a secondary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the secondary parameter list associated with the same secondary function signature definition, when a matching primary function signature definition is not found in the first data store.
12 Assignments
0 Petitions
Accused Products
Abstract
A method for parsing and verifying the contents of a command script containing a token and written in a scripting language. A first, relatively rapidly accessible data store and a second, less rapidly accessible data store are provided. Each data store contains function signature definitions which include a function name and an associated parameter list of zero or more parameter specifications. The first data store contains function names associated with commands that do not require data retrieval for completion. The second data store contains function names associated with commands that, unlike those in the first data store, do require data retrieval for completion. A potential function name and its associated arguments, if any, are recognized within the token. The first data store is searched for a matching function signature, having a function name matching the potential function name, and a parameter list matching the parsed potential function arguments. If no match is found, the second data store is then searched in a similar manner for a matching function signature.
184 Citations
13 Claims
-
1. A computerized method for parsing and verifying the contents of a command script submitted for execution, comprising the steps of:
-
providing a command script including at least one token and written in a scripting language;
providing a first, substantially rapidly-accessible data store containing at least one primary function signature definition including a primary function name that is associated with an operational command that does not require data retrieval for completion, and a primary parameter list associated with the primary function name and having zero or more parameter specifications;
providing a second data store that is less substantially rapidly-accessible than the first data store, the second data store containing at least one secondary function signature definition including a secondary function name that is associated with a command that requires data retrieval for completion, and a secondary parameter list associated with the secondary function name and having zero or more parameter specifications;
recognizing at least one portion of the at least one token to potentially represent a reference to a previously defined function in the scripting language, the potential function reference having a potential function name and zero or more potential parameters associated therewith;
searching the first data store for a matching primary function signature definition having a primary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the primary parameter list associated with the same primary function signature definition; and
searching the second data store for a matching secondary function signature definition having a secondary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the secondary parameter list associated with the same secondary function signature definition, when a matching primary function signature definition is not found in the first data store. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A computerized method for providing a user-extensible scripting language, comprising the steps of:
-
storing a user-defined function written in the scripting language in a data store, the user-defined function including at least one parameter associated therewith, and a body portion including at least one substitution symbol indicating that the value of the at least one parameter is to be inserted as text in place of the substitution symbol;
storing a function signature identifying characteristics of the user-defined function in the data store, the function signature including the name of the user-defined function and a specification of the at least one parameter;
recognizing a command script written in the scripting language to include a token containing a reference to the user-defined function and at least one parameter value associated therewith;
retrieving a copy of the body portion of the user-defined function referenced in the command string;
replacing the at least one substitution symbol within the copy with the at least one parameter value of the token;
reinterpreting the body of the copy of the user-defined function using the scripting language; and
recognizing the body of the copy of the user-defined function to include a token comprising a reference to a function which was not present in the body of the user-defined function in the data store, whereby a run-time interpretation of the user-defined function is altered to include an invocation of a function that was not contained within the previously stored user-defined function. - View Dependent Claims (13)
-
Specification