WO2008130769A2 - Runtime translation from late-bound to early-bound expression - Google Patents

Runtime translation from late-bound to early-bound expression Download PDF

Info

Publication number
WO2008130769A2
WO2008130769A2 PCT/US2008/057749 US2008057749W WO2008130769A2 WO 2008130769 A2 WO2008130769 A2 WO 2008130769A2 US 2008057749 W US2008057749 W US 2008057749W WO 2008130769 A2 WO2008130769 A2 WO 2008130769A2
Authority
WO
WIPO (PCT)
Prior art keywords
bound
early
late
expression
component
Prior art date
Application number
PCT/US2008/057749
Other languages
English (en)
French (fr)
Other versions
WO2008130769A3 (en
Inventor
David E. Sceppa
Carl Y. Perry
Jeffrey M. Derstadt
Andrew J. Conrad
Amanda K. Silver
Paul A. Vick
Shyamalan Pather
Colin Joseph Meek
Original Assignee
Microsoft Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from US11/940,029 external-priority patent/US8255883B2/en
Application filed by Microsoft Corporation filed Critical Microsoft Corporation
Publication of WO2008130769A2 publication Critical patent/WO2008130769A2/en
Publication of WO2008130769A3 publication Critical patent/WO2008130769A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45504Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
    • G06F9/45516Runtime code conversion or optimisation

Definitions

  • the subject specification relates generally to data structures and in particular to translation of data structure expressions.
  • Computer operations are commonly performed through instruction sets generally referred to as a programming languages.
  • Programming languages are conventionally based upon a common syntax that enables a programmer to write commands in the language. For instance, entry of '++' allows a number to be incremented in some programming languages. It is possible that various operators perform conflicting commands between two different programming languages - moreover, functions can be performed by separate commands. In an illustrative instance, to call a function, one language can use 'printf while a separate language uses 'disp'.
  • the subject innovation modifies a late -bound structure output of a compiler into an early-bound structure. Modification takes place through replacing a late-bound property accessor with an early-bound call.
  • the early-bound structure can translate into an expression tree such that the expression tree allows generation of a store specific query operated upon a database. Modification of the late-bound expression can occur at runtime, where a visitor pattern is used to create the modification.
  • the subject innovation goes against common industry thought and market trends.
  • FIG. 1 illustrates a representative system for conversion of a late-bound expression to an early-bound expression in accordance with an aspect of the subject specification.
  • FIG. 2 illustrates a representative alteration component in accordance with an aspect of the subject specification.
  • FIG. 3 illustrates a representative system with a compiler component and storage in accordance with an aspect of the subject specification.
  • FIG. 4 illustrates a representative late -bound expression in accordance with an aspect of the subject specification.
  • FIG. 5 illustrates a representative early-bound expression in accordance with an aspect of the subject specification.
  • FIG. 6 illustrates a representative query generation methodology in accordance with an aspect of the subject specification.
  • FIG. 7 illustrates a representative alteration methodology in accordance with an aspect of the subject specification.
  • FIG. 8 illustrates a representative modification methodology in accordance with an aspect of the subject specification.
  • FIG. 9 illustrates a representative methodology for performing checks in relation to translating a structure from late-bound to early-bound in accordance with an aspect of the subject specification.
  • FIG. 10 illustrates an example of a schematic block diagram of a computing environment in accordance with the subject specification.
  • FIG. 11 illustrates an example of a block diagram of a computer operable to execute the disclosed architecture.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a controller and the controller can be a component.
  • One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
  • an interface can include I/O components as well as associated processor, application, and/or API components.
  • the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter.
  • article of manufacture as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.
  • computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips%), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)...), smart cards, and flash memory devices (e.g., card, stick, key drive).
  • a carrier wave can be employed to carry computer-readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN).
  • LAN local area network
  • the word "exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion.
  • the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, "X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances.
  • the query is expressed as a string and validation occurs at run-time. Invalid data type comparisons, typos, etc. are not detected until run-time in a general case.
  • framework queries a language compiler validates a query at compile time using metadata for classes referenced in the query. For example, in the previous query, the compiler knows about the data type for the Contact class' Age property and knows how to evaluate the comparison to 40.
  • a developer can express a similar query. Developers can use a framework to map classes and properties to database tables and columns. The framework then translates the query at runtime to a database query, executes the query, and returns the results in terms of the class(es) specified.
  • a developer can construct a similar framework query:
  • the Contact class does not exist at compile time. There is creation of the class at runtime during the call to DynamicContext.CreateContext. [0029]
  • the code compiles because some languages can support a late-bound mode, deferring validation of code until runtime. There is little to no enforcement of type checking until runtime (e.g., at compile time). It assumes that the context object will have a Contacts property at runtime, and that the objects returned by the Contacts property will have properties for Age and LastName. This process is generally referred to as late binding.
  • FIG. 1 discloses an example system 100 for translating a late-bound expression into an early-bound expression.
  • a property of an object When operating with a late-bound expression, it is commonly not known if a property of an object will exist until a program is run. If the property does not exist, then various runtime errors can take place, causing application difficulties. With use of an early-bound expression, it can be known what classes/properties exist, thus eliminating errors that are caused by calling non-existent classes.
  • a compiler component transfers a late-bound expression to an obtainment component 102, where the obtainment component 102 collects a late-bound structure.
  • the obtainment component 102 can configure in a number of different embodiments.
  • the obtainment component 102 seeks out various compiler components.
  • the obtainment component 102 extracts the expression and retains the expression in local storage.
  • the obtainment component 102 can also operate as a passive unit, which receives information transmitted from a compiler component.
  • the obtainment component 102 can operate in a wireless manner, hard- wired manner, etc.
  • the obtainment component 102 conveys the late-bound expression to an alteration component 104.
  • the alteration component 104 converts a late-bound structure into an early-bound structure - commonly operating at runtime (e.g., operation of computer program execution).
  • the alteration component 104 can operate as a means for translating a late-bound expression into an early-bound expression.
  • FIG. 2 discloses an example alteration component 104 in accordance with an aspect of the subject specification.
  • a correspondence component 202 enables the alteration component 104 to interact with other units (e.g., a compiler component).
  • the correspondence component 202 can be utilized to enable devices of the alteration component 104 to engage other devices in a wireless manner, through a hard wire configuration, etc.
  • Security features can be implemented by the correspondence component 202, such as checking for errors that can disrupt the alteration component 104 and/or the system 100 of FIG. 1 (e.g., if a compiler is not operating appropriately, then mistakes can be identified by the correspondence component 202 and attempted repairs can take place.)
  • the correspondence component 202 can function as a means for passing the early-bound expression to an entity implementation.
  • An analysis component 204 evaluates the collected late-bound structure. In order to change a late-bound structure into an early-bound structure, characteristics should be ascertained relating to the structure. For instance, the analysis component 204 can use a visitor pattern to convert the collected late-bound structure.
  • a visitor pattern is a behavioral type of design pattern that separates an algorithm from an object structure.
  • the analysis component 204 can operate as a means for analyzing the late -bound expression.
  • a change component 206 transforms at least a portion of the structure to a strong type. Strong typing allows information to be checked in such a manner that there are minimal errors that can take place at runtime.
  • data types of a compiled structure can be allocated restrictions so modification cannot take place upon the types that would cause an error.
  • Artificial intelligence component 208 makes at least one inference or at least one determination about conversion of the late-bound structure into the early- bound structure.
  • Artificial intelligence component 208 can function as a processor for the alteration component 104.
  • the artificial intelligence component 208 can infer when a compiler component has finished sending a late-bound expression (e.g., an amount of time has passed with no data transmission from the compiler component).
  • the artificial intelligence component 208 can make a determination, such as how quickly an operation should take.
  • Artificial intelligence component 208 can employ one of numerous methodologies for learning from data and then drawing inferences and/or making determinations related to profile creation (e.g., Hidden Markov Models (HMMs) and related prototypical dependency models, more general probabilistic graphical models, such as Bayesian networks, e.g., created by structure search using a Bayesian model score or approximation, linear classifiers, such as support vector machines (SVMs), non-linear classifiers, such as methods referred to as "neural network” methodologies, fuzzy logic methodologies, and other approaches that perform data fusion, etc.) in accordance with implementing various automated aspects described herein.
  • HMMs Hidden Markov Models
  • Bayesian networks e.g., created by structure search using a Bayesian model score or approximation
  • linear classifiers such as support vector machines (SVMs)
  • SVMs support vector machines
  • non-linear classifiers such as methods referred to as "neural network” methodologies, fuzzy logic methodologies, and other approaches
  • Methods also include methods for the capture of logical relationships such as theorem provers or more heuristic rule-based expert systems.
  • a modification component 210 arranges the early-bound structure into a tree.
  • a tree allows for a breakdown of an operation to be followed in a dependent manner - various constructs are dependent upon other constructs.
  • a comparator can relate toward two arguments - without the arguments, there would be little to compare.
  • the modification component 210 can operate as a means for modifying the early-bound query to a tree.
  • a creation component 212 generates a store-specific query based upon the early-bound structure.
  • the creation component 212 allows an ability to translate the early-bound expression into database queries (e.g., DbCommands) that can execute against a database. Operation of the creation component 212 allows leveraging of a framework remainder.
  • the creation component 212 can operate as a means for generating a store specific query based upon the early-bound expression.
  • FIG. 3 discloses an example system 300 disclosing additional operation units for translation of a late-bound expression to an early-bound expression.
  • a compiler component 302 modifies source language into a target language; output of the compiler component 302 is generally a late-bound expression.
  • the compiler component 302 can function as a means for changing source code into the late-bound expression.
  • the compiler component 302 can support checking against the types would be generated such that the compiler component 302 would disclose items such as types did not match or that a property will not be there at run time, etc.
  • An obtainment component 102 collects a late-bound structure produced by the compiler component 302.
  • a transfer component 104 converts a late-bound structure into an early-bound structure.
  • the transfer component 104 can modify the early-bound structure into a tree (e.g., a DbCommandTree) that enables development of a store specific query.
  • a store specific query is operated upon storage 304, commonly to obtain information from a database (e.g., though a structured query language).
  • Storage 304 can have a number of different configurations, including as flash memory, battery backed memory, magnetic tape, hard disk, etc.
  • the alteration component 104 can configure to operate the query upon the storage (e.g., though utilization of the creation component 212 of FIG. 2) and to transfer results of the query to an auxiliary location (e.g., transmission from the correspondence component 202).
  • Various other components can utilize the storage 304.
  • the obtainment component 102 can place gathered contents upon the storage 304 and operations are performed upon saved gathered contents.
  • FIG. 4 discloses an example tree 400 that enters the obtainment component 102 of FIG. 1.
  • FIG. 4 can use a declaration:
  • the tree 400 discloses how the expression is being evaluated.
  • Method 402 makes a call to a method to envoke the method and thus executes the method (e.g., IQueryable is an interface associated with the method).
  • the request 402 returns an object and breaks down into an object and an argument 404.
  • the argument 404 is a lambda expression and can output an object instance 406.
  • a where method call 408 from the expression provides an execution of a preconditioned method.
  • Another lambda expression 410 is exposed, thus producing a comparator 412 (e.g., an equal sign).
  • a string 414 is used to specify characteristics sought in a query expression.
  • a method 416 is used to operate the 'c.
  • the method call 408 can output an expression 422.
  • FIG. 5 discloses an example tree 500 that exits the transfer component 104 of FIG. 1.
  • FIG. 5 can use the same declaration and expression as disclosed in FIG.
  • variable term 'object' e.g., return type
  • the tree 500 discloses how the expression is being evaluated.
  • Request 502 makes a call to a method to envoke the method and thus execute the method (e.g.,
  • IQueryable is an interface associated with the method).
  • the request 502 returns an object and breaks down into an object and an argument 504.
  • the argument 504 is a lambda expression and can output an object instance 506.
  • method call 508 can enable execution a preconditioned method.
  • Another lambda expression 510 is exposed, thus producing a comparator 512 (e.g., an equal sign).
  • a string 514 is used to determine characteristics of a color 'blue'.
  • Latebindings e.g., the method 416, property 418 and identifier 420 of FIG. 4 are removed and replaced with a statically typed call 516 and an object identifier 518.
  • the method call 508 can output an expression 520 valued at cars of car.
  • Operation of the tree 500 creates a static type for 'cars' at runtime. It is understood that objects in 'cars' is a car, and the type was not generated.
  • FIG. 6 discloses an example methodology 600 for operating a query upon a database. There is walking through a late-bound expression generated by a compiler 602. Walking through provide evaluated characteristics that can be used to transform a late-bound expression. Examination of an object can take place in order to determine a return type. For instance, if there is a generic object, then walking through can determine that the object is specifically 'cars.' [0055] Translating late-bound expressions into a new early-bound expression 604 occurs.
  • Action 604 takes place through replacing of at least one method call of the late-bound expression with a statically typed call. Translation allows for types of the expression to convert to strongly typed since types can be known due to the replaced method calls.
  • Passing the new early-bound expression to a specific implementation 606 takes place.
  • Event 608 is converting the early-bound expression into a tree. The combination of act 606 and event 608 enables alters the early-bound expression into a flow structure.
  • a store-specific query allows information to be retrieved from a database. For instance, a programmer can write programming code intended to run a query upon a database (e.g., a request to call cars that are colored blue).
  • a compiler outputs a late-bound expression showing an object and translation of the expression converts the object to a specific term 'cars' at runtime.
  • a query is then applied in a framework implementation to return a list of cars that are colored blue.
  • FIG. 7 discloses an example methodology 700 for manipulation of an early-bound structure to a late-bound structure through method call replacement.
  • the methodology 700 can implement principles modifying an expression tree 400 of FIG. 4 to an expression tree 500 of FIG. 5.
  • IQueryable source element type is changed from Object to generated runtime type (Car). This can take place with regard to the expression 520 of FIG. 5
  • Replacing a late-bound property with an early-bound call 704 occurs.
  • the statically typed call enables an early-bound configuration since a specific object (e.g., Car) is now known up completion of compiler operation.
  • Event 704 replaces the method 416, property 418 and identifier 420 of FIG. 4 with an early-bound call 516 and an object identifier 518 of FIG. 5
  • a Predicate Lambda expression type can be changed to runtime type (e.g., Car). This alters a lambda expression 410 of FIG.
  • Action 708 is transferring return type to a runtime type.
  • Return type of Where MethodCallExpression can be changed to runtime type (e.g., Car).
  • runtime type e.g., Car
  • This can change the method call 404 of FIG. 4 with the method call 504 of FIG. 5.
  • There is chancing a selector Lambda expression type is changed to runtime type (e.g.,
  • FIG. 8 discloses an example late-bound to early-bound transition methodology 800. There is receiving a late-bound method call from a compiler 802. At compile time, a compiler generates a late-bound expression in a target language from computer code written in a source language. Reception can take place according to various embodiments, including wireless transmission, hard- wired communication, etc.
  • a visitor pattern 804 takes place.
  • a visitor pattern can be utilized in order to change the early-bound expression; however, different visitor patterns can be used. For instance, specific functions that are commonly used in a visitor pattern for a target language are determined (e.g., though use of artificial intelligence techniques).
  • FIG. 9 is an example methodology 900 for determining if a transition between late-bound to early-bound can take place.
  • a compiler 902. Reception can take place wirelessly, in a hard-wired configuration, in an encrypted manner, etc.
  • a check 904 takes place to determine if a late-bound structure can be converted into an early-bound expression. If a conversion cannot and/or should not take place, then there can be performing runtime with late-bound structure 906. There can be translating late-bound expression into early-bound expression 908. This can take place in a manner consistent disclosed in other portions of the subject specification (e.g., through replacing method calls with early-bound calls).
  • a check 912 can occur to determine if there is to be a store specific query. There can be performing an auxiliary operation 914 if a query is not to take place. Generating a store-specific query 916 can take place to obtain information from a database.
  • Other actions can associate with the methodology 900 concerning application of the generated store specific query. For instances, there can be testing the query, applying the query upon a database, collecting and/or processing results of the query, etc.
  • language integrated query is used to indicate that query is an integrated feature of the developer's primary programming languages (e.g., C#, Visual Basic).
  • Language integrated query allows query expressions to benefit from the rich metadata, compile-time syntax checking, static typing and IntelliSense that was previously available only to imperative code.
  • Language integrated query also allows a single general-purpose declarative query facility to be applied to all in- memory information, not just information from external sources.
  • the extensibility of the query architecture is used to provide implementations that work over both general markup language and structured query language data.
  • the query operators over general markup language can use an efficient, easy-to-use in-memory facility to provide certain functionality in the host programming language.
  • the query operators over relational data (DLinq) build on the integration of structure query language-based schema definitions into virtual machine type system. Integration provides strong typing over relational data while retaining the expressive power of the relational model and the performance of query evaluation directly in the underlying store.
  • DLinq relational data
  • FIGs. 10 and 11 are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a program that runs on one or more computers, those skilled in the art will recognize that the subject matter described herein also can be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.
  • inventive methods can be practiced with other computer system configurations, including single-processor, multiprocessor or multi-core processor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., personal digital assistant (PDA), phone, watch%), microprocessor-based or programmable consumer or industrial electronics, and the like.
  • PDA personal digital assistant
  • the illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • FIG. 10 there is illustrated a schematic block diagram of a computing environment 1000 in accordance with the subject specification.
  • the system 1000 includes one or more client(s) 1002.
  • the client(s) 1002 can be hardware and/or software (e.g., threads, processes, computing devices).
  • the client(s) 1002 can house cookie(s) and/or associated contextual information by employing the specification, for example.
  • the system 1000 also includes one or more server(s) 1004.
  • the server(s) 1004 can also be hardware and/or software (e.g., threads, processes, computing devices).
  • the servers 1004 can house threads to perform transformations by employing the specification, for example.
  • One possible communication between a client 1002 and a server 1004 can be in the form of a data packet adapted to be transmitted between two or more computer processes.
  • the data packet may include a cookie and/or associated contextual information, for example.
  • the system 1000 includes a communication framework 1006 (e.g., a global communication network such as the Internet) that can be employed to facilitate communications between the client(s) 1002 and the server(s) 1004. [0081] Communications can be facilitated via a wired (including optical fiber) and/or wireless technology.
  • the client(s) 1002 are operatively connected to one or more client data store(s) 1008 that can be employed to store information local to the client(s) 1002 (e.g., cookie(s) and/or associated contextual information).
  • the server(s) 1004 are operatively connected to one or more server data store(s) 1010 that can be employed to store information local to the servers 1004.
  • FIG. 11 there is illustrated a block diagram of a computer operable to execute the disclosed architecture.
  • FIG. 11 and the following discussion are intended to provide a brief, general description of a suitable computing environment 1100 in which the various aspects of the specification can be implemented.
  • program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
  • inventive methods can be practiced with other computer system configurations, including single- processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.
  • the illustrated aspects of the specification may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network.
  • program modules can be located in both local and remote memory storage devices.
  • a computer typically includes a variety of computer-readable media.
  • Computer-readable media can be any available media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and nonremovable media.
  • Computer-readable media can comprise computer storage media and communication media.
  • Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.
  • Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media.
  • modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.
  • the example environment 1100 for implementing various aspects of the specification includes a computer 1102, the computer 1102 including a processing unit 1104, a system memory 1106 and a system bus 1108.
  • the system bus 1108 couples system components including, but not limited to, the system memory 1106 to the processing unit 1104.
  • the processing unit 1104 can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be employed as the processing unit 1104.
  • the system bus 1108 can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures.
  • the system memory 1106 includes read-only memory (ROM) 1110 and random access memory (RAM) 1112.
  • ROM read-only memory
  • RAM random access memory
  • a basic input/output system (BIOS) is stored in a non- volatile memory 1110 such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 1102, such as during start-up.
  • the RAM 1112 can also include a high-speed RAM such as static RAM for caching data.
  • the computer 1102 further includes an internal hard disk drive (HDD) 1114 (e.g., EIDE, SATA), which internal hard disk drive 1114 may also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 1116, (e.g., to read from or write to a removable diskette 1118) and an optical disk drive 1120, (e.g., reading a CD-ROM disk 1122 or, to read from or write to other high capacity optical media such as the DVD).
  • the hard disk drive 1114, magnetic disk drive 1116 and optical disk drive 1120 can be connected to the system bus 1108 by a hard disk drive interface 1124, a magnetic disk drive interface 1126 and an optical drive interface 1128, respectively.
  • the interface 1124 for external drive implementations includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies. Other external drive connection technologies are within contemplation of the subject specification.
  • USB Universal Serial Bus
  • Other external drive connection technologies are within contemplation of the subject specification.
  • the drives and their associated computer-readable media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth.
  • the drives and media accommodate the storage of any data in a suitable digital format.
  • a number of program modules can be stored in the drives and RAM 1112, including an operating system 1130, one or more application programs 1132, other program modules 1134 and program data 1136. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 1112.
  • a user can enter commands and information into the computer 1102 through one or more wired/wireless input devices, e.g., a keyboard 1138 and a pointing device, such as a mouse 1140.
  • Other input devices may include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, touch screen, or the like.
  • These and other input devices are often connected to the processing unit 1104 through an input device interface 1142 that is coupled to the system bus 1108, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.
  • a monitor 1144 or other type of display device is also connected to the system bus 1108 via an interface, such as a video adapter 1146.
  • a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.
  • the computer 1102 may operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 1148.
  • the remote computer(s) 1148 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 1102, although, for purposes of brevity, only a memory/storage device 1150 is illustrated.
  • the logical connections depicted include wired/wireless connectivity to a local area network (LAN) 1152 and/or larger networks, e.g., a wide area network (WAN) 1154.
  • LAN local area network
  • WAN wide area network
  • LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise- wide computer networks, such as intranets, all of which may connect to a global communications network, e.g., the Internet.
  • the computer 1102 When used in a LAN networking environment, the computer 1102 is connected to the local network 1152 through a wired and/or wireless communication network interface or adapter 1156.
  • the adapter 1156 may facilitate wired or wireless communication to the LAN 1152, which may also include a wireless access point disposed thereon for communicating with the wireless adapter 1156.
  • the computer 1102 can include a modem 1158, or is connected to a communications server on the WAN 1154, or has other means for establishing communications over the WAN 1154, such as by way of the Internet.
  • the modem 1158 which can be internal or external and a wired or wireless device, is connected to the system bus 1108 via the serial port interface 1142.
  • program modules depicted relative to the computer 1102, or portions thereof can be stored in the remote memory/storage device 1150. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.
  • the computer 1102 is operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone.
  • any wireless devices or entities operatively disposed in wireless communication e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone.
  • the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.
  • Wi-Fi Wireless Fidelity
  • Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station.
  • Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity.
  • IEEE 802.11 a, b, g, etc.
  • a Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which use IEEE 802.3 or Ethernet).
  • Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps (802.1 Ia) or 54 Mbps (802.1 Ib) data rate, for example, or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic lOBaseT wired Ethernet networks used in many offices.
PCT/US2008/057749 2007-04-20 2008-03-20 Runtime translation from late-bound to early-bound expression WO2008130769A2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US91318607P 2007-04-20 2007-04-20
US60/913,186 2007-04-20
US11/940,029 US8255883B2 (en) 2007-04-20 2007-11-14 Translating late bound LINQ expressions into database queries
US11/940,029 2007-11-14

Publications (2)

Publication Number Publication Date
WO2008130769A2 true WO2008130769A2 (en) 2008-10-30
WO2008130769A3 WO2008130769A3 (en) 2011-06-16

Family

ID=39876136

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/057749 WO2008130769A2 (en) 2007-04-20 2008-03-20 Runtime translation from late-bound to early-bound expression

Country Status (1)

Country Link
WO (1) WO2008130769A2 (pt-BR)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105493033A (zh) * 2013-06-02 2016-04-13 微软技术许可有限责任公司 声明性配置元素
CN107704382A (zh) * 2017-09-07 2018-02-16 北京信息科技大学 面向Python的函数调用路径生成方法和系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7100153B1 (en) * 2000-07-06 2006-08-29 Microsoft Corporation Compiler generation of a late binding interface implementation
WO2006130871A2 (en) * 2005-06-02 2006-12-07 The Mathworks, Inc. Calling of late bound functions from an external program environment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7100153B1 (en) * 2000-07-06 2006-08-29 Microsoft Corporation Compiler generation of a late binding interface implementation
WO2006130871A2 (en) * 2005-06-02 2006-12-07 The Mathworks, Inc. Calling of late bound functions from an external program environment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHEN, Y. ET AL.: 'A language of fexible objects.' TECHNICAL REPORT 29, DEPARTMENT OF COMPUTER SCIENCE 2004, LEICESTER UNIVERSITY, *
PYSTER, A.: 'Using assertions to improve language translators' 1977 ACM NA TIONAL COMPUTER CONFERENCE 13 June 1977 - 16 June 1977, NEW YORK, pages 665 - 668 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105493033A (zh) * 2013-06-02 2016-04-13 微软技术许可有限责任公司 声明性配置元素
US10606569B2 (en) 2013-06-02 2020-03-31 Microsoft Technology Licensing, Llc Declarative configuration elements
CN107704382A (zh) * 2017-09-07 2018-02-16 北京信息科技大学 面向Python的函数调用路径生成方法和系统
CN107704382B (zh) * 2017-09-07 2020-09-25 北京信息科技大学 面向Python的函数调用路径生成方法和系统

Also Published As

Publication number Publication date
WO2008130769A3 (en) 2011-06-16

Similar Documents

Publication Publication Date Title
US8255883B2 (en) Translating late bound LINQ expressions into database queries
US5161216A (en) Interprocedural slicing of computer programs using dependence graphs
JP5354601B2 (ja) プロデューサグラフ指向のプログラミングフレームワークにおけるパラレル化及びインスツルメンテーション
JP5354602B2 (ja) プロデューサグラフ指向のプログラミング及び実行
Balci Requirements for model development environments
US8726231B2 (en) Support for heterogeneous database artifacts in a single project
WO2017095720A1 (en) Techniques to identify idiomatic code in a code base
Rodriguez-Prieto et al. An efficient and scalable platform for Java source code analysis using overlaid graph representations
WO2018222327A1 (en) Automated or machine-enhanced source code debugging
Yang et al. Powerstation: Automatically detecting and fixing inefficiencies of database-backed web applications in ide
WO2013184952A1 (en) Method for automatic extraction of designs from standard source code
US20240028316A1 (en) Preventing garbage object accumulation on minimal runtimes while supporting an implicit deallocation programming experience
WO2008130769A2 (en) Runtime translation from late-bound to early-bound expression
US11662998B2 (en) Detecting duplicated code patterns in visual programming language code instances
Wood et al. Supporting robotic software migration using static analysis and model-driven engineering
CN116391172A (zh) 用于创建和执行高度扩展的云应用的系统和方法
Dietrich et al. An ontology based representation of software design patterns
Jarraya et al. Quantitative and qualitative analysis of SysML activity diagrams
US11907223B2 (en) System and method for executing compiled user defined functions in vectorized databases
Stein et al. Graph-Based Source Code Analysis of Dynamically Typed Languages
Zhang et al. Java source code static check eclipse plug-in based on common design pattern
Afzal Modular Dependency Analysis in Heterogeneous Software Systems
Paen Measuring incrementally developed model transformations using change metrics
Stein et al. Graph-Based Source Code Analysis of JavaScript Repositories
Abbas et al. Formalizing and verifying UML activity diagrams

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08780486

Country of ref document: EP

Kind code of ref document: A2