Borland Software Corporation

Google Inc.

Christian Karl Kemper

Mark K Howe

Blake Stone

Michael Forster

Steffi Scherzinger

Ulf Adams

Lubomir B Litchev

William C Joy

Methods, systems, and computer-readable media for determining whether dependencies of configuration files have changed such that the compilation strategy should be recomputed. Local build checksums are computed for individual configuration files. The local build checksums are computed by sorting input paths to the configuration files plus data indicating whether the path refers to a file or a directory and a checksum computed on the configuration file itself. The transitive closure of local build checksums are then used to compute a global build checksum: the local build checksums are sorted in order to compute the global build checksum. If the global build checksum is different from a previously computed global build checksum, then the compilation strategy should be recomputed, since this is a signal that the compilation strategy may not be valid anymore, e.g. because some dependencies in the configuration files have changed.

Methods, apparatuses, and computer-readable media for computing checksums for effective caching in continuous distributed builds

A system and methodology for asynchronous code refactoring with symbol injection is described. In one embodiment, for example, a method is described for refactoring a plurality of interdependent software modules that reside in separate projects, the method comprises steps of: in response to a change that affects a particular symbol of a software module that resides in a first project, refactoring the software module of the first project to propagate the change to all instances of the particular symbol in the software module; during the refactoring of the software module of the first project, recording meta data about the refactoring that is required to effect the change; and automatically propagating the change to a dependent software module residing in a second project, by refactoring the dependent software module based on the recorded meta data about the refactoring that occurred to the software module of the first project.

System and methodology for asynchronous code refactoring with symbol injection

A system providing methods for adjusting a user's selection of source code of a program to correspond with a parsed version of the program is described. The method commences with user input of a selection of source code of a program for performing an operation such as a refactoring. The user's selection is compared with a parsed version of the program. If the user's selection does not correspond with the parsed version of the program, the user's selection is adjusted to achieve correspondence with the parsed version of the program.

System and methodology providing automated selection adjustment for refactoring

A system and methodology for providing a Unified Modeling Language (UML) diagram of a program for display in a graphical user interface of a development system is described. Relationships between a plurality of files of a program are determined using a compiler. When a request for display of a UML diagram is received, a UML diagram of the currently selected file is generated based upon the determined relationships between the currently selected file and other files of the program. The UML diagram displayed in the graphical user interface enables a user to navigate to a particular file of the program by selecting one of the nodes of the UML diagram. The system enables a user to view source code or a UML diagram of a particular component displayed in the UML diagram.

System and methodology for providing fixed UML layout for an object oriented class browser

A system providing an improved method for compiler-assisted refactoring of a software application is described. Upon receiving a request for refactoring of a software application (e.g., changing a given symbol of the application), the binary files of the application are parsed to identify those binary files containing references to the given symbol. The source files of the identified binary files are then retrieved and fed into a compiler. The compiler is used to generate a list of all uses of the given symbol in the software application. This list includes not only the text name of the symbol, but also type information and position information regarding its location(s) in the source file. Based upon the list, changes are applied to the software application.

Growing community of inventors

Santa Cruz, CA, United States of America

Christian Karl Kemper