An aspect provides a computer-implemented method for processing computer code. The method comprises receiving a first editable code set. In response to a first signal the method processes the first editable code set into first executable code by a first compiler within a first code processing path generating the first executable code. In response to a second signal the method both processes the first editable code set into a second editable code set, and processes the second editable code set into second executable code by a second compiler within a second code processing path generating the second executable code.

Implementations are described herein for leveraging prior source code transformations to facilitate automatic creation and/or recommendation of tools for automating aspects of source code transformations captured in real time. In various implementations, a transformation made by a programmer to a source code snipped may be captured in a source code editor application in real time. Based on the transformation and the intent, one or more candidate source code transformations may be identified from one or more repositories of prior source code transformations made by one or more other programmers. The source code editor application may be caused to provide output indicative of a tool that is operable to automate one or more edits associated with both the transformation made by the programmer to the source code snippet and with one or more of the candidate source code transformations.

Implementations are described herein for leveraging prior source code transformations to facilitate automatic creation and/or recommendation of tools for automating aspects of source code transformations captured in real time. In various implementations, a transformation made by a programmer to a source code snipped may be captured in a source code editor application in real time. Based on the transformation and the intent, one or more candidate source code transformations may be identified from one or more repositories of prior source code transformations made by one or more other programmers. The source code editor application may be caused to provide output indicative of a tool that is operable to automate one or more edits associated with both the transformation made by the programmer to the source code snippet and with one or more of the candidate source code transformations.

Disclosed herein are techniques for automatically reconfiguring code based on function and subfunction analysis. Techniques include determining, by parsing a code structure representing a plurality of functions, that at least one first function has a threshold degree of complexity; identifying, in response to the determination, a plurality of subfunctions based on the at least one first function, the plurality of subfunctions having a commonality with the at least one first function; and forming a second function by reconfiguring the first function to call at least one of the identified plurality of subfunctions.

An information processing device, includes a memory; and a processor coupled to the memory and configured to: generate second data by adding, to first data including a machine language, first machine language data that may be destroyed at a time of transfer of the first data and second machine language data that is not destroyed at the time of the transfer, and transmit the second data.

In some implementations, a device may receive source code associated with an application program interface (API) configured to execute on a dedicated runtime infrastructure. The device may generate an executable policy document including machine-readable text based on one or more code sections in the source code that implement one or more function calls associated with one or more function call types. The device may invoke a validation utility to cross-check the executable policy document against a design document associated with the API. The device may deploy the executable policy document in a common runtime environment that includes a shared runtime infrastructure to support multiple executable policy documents based on the validation utility indicating that the executable policy document satisfies functional requirements described in the design document associated with the API.

In some implementations, a device may receive source code associated with an application program interface (API) configured to execute on a dedicated runtime infrastructure. The device may generate an executable policy document including machine-readable text based on one or more code sections in the source code that implement one or more function calls associated with one or more function call types. The device may invoke a validation utility to cross-check the executable policy document against a design document associated with the API. The device may deploy the executable policy document in a common runtime environment that includes a shared runtime infrastructure to support multiple executable policy documents based on the validation utility indicating that the executable policy document satisfies functional requirements described in the design document associated with the API.

Disclosed is a method for communication between two devices or between an application and the device on which the application is running. The method uses a text or natural language based syntax in the creation of a library of text language elements. An approval computing device can approve the associations of the library. The library may be transmitted to a second computing device with a message. The text language elements are converted to computer executable code by a text language module or text language application running on the device.

Disclosed is a method for communication between two devices or between an application and the device on which the application is running. The method uses a text or natural language based syntax in the creation of a library of text language elements. An approval computing device can approve the associations of the library. The library may be transmitted to a second computing device with a message. The text language elements are converted to computer executable code by a text language module or text language application running on the device.

In one implementation, a method for automatically generating a security policy for a controller includes receiving, by a security policy generation system and from a controller development environment, code for a device controller; selecting middleware that enforces a security policy; analyzing the code for the device controller; based at least in part on the analyzing, automatically generating the security policy; and providing the selected middleware along with the generated security policy.