64 results about "Declaration" patented technology

The invention relates to a method for enhancing an object-oriented programming language. The method includes declaring one or more class structures in databases having metadata describing characteristics defining the class structures. The method also includes extending the metadata associated with the class structures by adding any number of additional metadata to the databases.

The mechanism includes three data structures: object data associated with each object O1, O2, O3 ... of a program, a class descriptor associated with the classes to which the objects O1, O2, O3 ... belong, and interface references. For each class Ci, the class descriptor corresponding to the class Ci includes: i) a class method table comprising one or more entries, wherein each entry identifies an implementation of a method inherited or defined by the class Ci; and ii) for each interface implemented by the class Ci, an interface method table comprising one or more entries, wherein each entry identifies an implementation of a method declared by the particular interface or an implementation of a method declared by an interface extended by the particular interface. An interface reference for an interface declaration ID associated with a given object OI, wherein the object OI implements methods that are declared by an interface declaration ID includes a pointer to the interface method table corresponding to the interface declaration ID within the class descriptor corresponding to the object OI. An efficient mechanism for method invocations is provided by generating an index that identifies the entry corresponding to the appropriate method in the interface method table pointed to by the pointer of the interface reference, reading the data stored by the entry identified by the index, and controlling the computer processing apparatus to jump to the address identified by the data.

A method includes receiving a portion of JAVA™ language software having a declaration of an instance of a generic class, parsing the declaration into a token corresponding to the generic class, and generating an intermediate language code block corresponding to the parsed declaration. The intermediate language code block is executable by a runtime engine. A system for compiling includes a parser receiving JAVA™ language source code having an instruction referencing a generic class and specifying a type of the generic class, and a code generator generating intermediate language code representing the source code.

A programming language syntax that embeds object type declaration in the object name. The objects are self-documenting because its object type is embedded in each object. In one embodiment, the object type-declaration prefix precedes the object name and explicitly declares the object type information. For example, a SQL object FirstName, may be implemented as SQL@FirstName, a URL object may be implemented as URL@FirstName, environment object from an environment table may be implemented as ENV@user.

A method and system for instructing a computer in a system of a declarative computer programming language. Unlike traditional declarative languages, the programming language may be neither relational nor functional, neither procedural nor imperative. The declarative elements may be defined as a meta-description of logic and data. The basic morphology of this meta-description may be a data construct known as a Lattice. Lattices derive declarative power from their inclusion of “Attributes” and “Sites”. Attributes are declarative properties that determine the internal behavior of a Lattice; while Sites are declarative data access points that establish the external relationship a Lattice may have with other Lattices, Lattice Containers, and Lattice Elements. Each of these data constructs are highly adaptable, recursive, and expandable, providing the entire language with a degree of flexibility that facilitates a very high level of abstraction.

An asynchronous execution process to allow a compiler or interpreter to recognize code elements that may be executed out of order and to create a light weight thread for execution of the code element. This light weight thread may be executed on another processor in a multiprocessing environment. An “async” keyword is included in a language to indicate that a statement may be executed asynchronously with respect to the other statements at the same nesting level. The “async” keyword may also be used to modify the declaration of a function to indicate that it is safe to run the affected method out of order with other statements in a block. An “async_end” keyword is included in a language to indicate that asynchronous execution of a statement, block of code, or method must be complete before the next statement, block of code, or method may be executed.

In a process of developing software applications from software components, the validity of component interactions is automatically validated by a program that determines a permission statement for any given utilization of a server component (305) by a client component (307). In a predefined structure (211–272), descriptors (211–219) are assigned (231–239) to components (301–309), descriptors (220–225) are assigned (241–255) to descriptors (211–224), some descriptors (223) have declarations to components (305), and some descriptors (217) have declarations to descriptors (223). The permission statement is true when 4 predefined conditions are all in compliance. The conditions are defined in relation to a common descriptor (225), to client (217) and server (223) intermediate descriptors, and to first (261) and second (262) declarations.

A front end component and a technique are provided. The front end component allows a transformation rule writer to specify syntax structure of interest, as well as what action to take when a syntax structure of interest is found. Example syntax structures include function call, variable declaration, math expression, etc. Typical actions include matching, replacement, or copying. The technique allows transformation tool writers to translate the specification into actual query and manipulation commands on the program representation. It is structured to be target language agnostic and, therefore, can be easily re-targeted to different programming languages.

Methods and systems are described herein for extending configuration dependent extensible software programs. Classes of a core extensible software program may be extended by adding a configuration dependent extension. The extensions may be added statically prior to compiling the core version of a software program or dynamically at runtime. The declaration of extensible core classes may include an extensibility attribute with an indication of whether the class is statically extensible or dynamically extensible. An object description language is also described herein for appropriately declaring configuration dependent extensible classes. Also, a preprocessor is described herein for processing the object description language to generate a source code representation of the extensible class declarations and their extensions. The source code representation may then be used to generate the extended version of the core software program.

Aspects extend to methods, systems, and computer program products for using declarative configuration data to manage cloud lifecycle. A declarative language can be used to declare physical and logicaltopology as well as lifecycle management commands at multiple topology hierarchies. Developers of different cloud components can declare roles and cloud operations in compliance with a declaration model. Compliance with the declaration model allows aggregation and cross-referencing among commands and topology elements declared by different developers. As such, dependencies between components canbe efficiently identified and accounted for when implementing lifecycle management commands. Declarative configuration data can also be used to onboard additional components to a cloud without code changes to an underlying lifecycle state manager.