International Business Machines Corporation

Sarika Sinha

Vikas Chandra

Sandeep Kohli

Siddharth Kumar Saraya

Srinivasan S Muthuswamy

Pradeep Kumar Rathi

Madhu Pavan Kothapally

Bharath Sakthivel

Rajesh Kumar Pirati

An example operation may include one or more of receiving, via a user interface, a feature set, querying a repository of application programming interfaces (APIs) to identify an API in the repository that corresponds to the received feature set based on a comparison of features in the feature set to features of the API stored in the repository, identifying criteria of the identified API that is published in the repository, and displaying a recommendation with the identified API including the identified criteria of the identified API via the user interface.

API repository with searchable feature set

Tasks are selected for hibernation by recording user preferences for tasks having no penalty for hibernation and sleep; and assigning thresholds for battery power at which tasks are selected for a least one of hibernation and sleep. The assigning of the thresholds for battery power include considering current usage of hardware resources by a user and battery health per battery segment. A penalty score is determined for tasks based upon the user preferences for tasks having no penalty, and task performance including at least one of frequency of utilization, memory utilization, task dependency characteristics and task memory hierarchy. The penalty performance is a value including both the user preference and the task performance. Tasks can then be put into at least one of hibernation mode and sleep mode dictated by their penalty performance during the thresholds for battery power.

Hibernation of computing device with faulty batteries

An approach is provided for predicting an exception during a debugging of software code before the debugging encounters the exception. During a debugging of a line number L of the code and based on an exception being predicted to be encountered at a line number M, a warning is displayed that the exception is to be encountered at the line number M, which is within a range of line numbers L+1 through L+X, where L&#x3e;0 and X&#x3e;1. Using a fix written in response to the predicted exception, the software code is modified. During a debugging of the line number M of the code, the modified software code is executed to avoid the predicted exception.

Exception prediction before an actual exception during debugging

An approach is provided for predicting an exception during a debugging of software code before the debugging encounters the exception. A number of lines X is received. During a debugging of a line number L of the code, upcoming lines consisting of line numbers L+1 through L+X are executed. Based on the execution of the upcoming lines, the exception is predicted to be encountered at line number M, which is within a range of line numbers L+1 through L+X. During the debugging of the line number L, and based on the prediction and the line number being within the range, a warning is displayed that the exception is to be encountered at line number M.

Systems, methods and tools for identifying potential errors or inconsistencies occurring during the runtime of multi-threaded applications and reporting the errors to a user, administrator or developer for correction and adjustments to the program code or thread timings. Embodiments of the disclosure capture thread sequences during a runtime or simulation environment and store the thread sequences as a matrix or tabular representation in a file. Multi-threaded application runs having an error free thread sequence, may be used as benchmarks for identifying potential errors and mis-runs of variations to the multi-threaded application as changes occur to the application code or new threads are added to the application code. This comparison may be performed by comparing the captured thread sequences of both the passing run and the mis-run of the multi-threaded application for differences in the thread sequences that may have caused the mis-run to occur.

Multi-thread sequencing

An approach is provided for predicting an exception during debugging of software code before the debugging encounters the exception. A number of lines X is received. A line number L of the code is debugged. In a new thread, upcoming lines consisting of line numbers L+1 through L+X are executed. Based on the execution of the upcoming lines, a prediction is determined that the exception will be encountered at line number M, which is within a range of line numbers L+1 and L+X. Based on the prediction and the line number being within the range, a warning is displayed that the exception is likely to be encountered at line number M. Responsive to the displayed warning, an indication that a corrective action was taken to avoid the exception is received.

A user selection of an item corresponding to a Web page can be received. The user selection can represents a request to open the Web page within an instantiated one of a set of Web browser applications installed on a computing device. A set of Web page elements unique to the Web page can be identified through an analysis conducted by the computing device. The identified set of Web page elements can be utilized to determine at the computing device one of the installed Web browser applications for the Web page. The determination of the one installed Web browser application can varies from Web page-to-Web page. At the computing device, the determined one of the Web browser applications can be instantiated. The Web page can be opened within the instantiated one of the Web browser applications.

Dynamic selection of one of many available web browsers

Inheritance contributions of programming class functions and class variables are diagrammed. A functional diagram illustrates individual class contributions of functions. A variable composition diagram illustrates individual class contributions of variables. A diagrammatic depiction of functions overridden and functions contributed in the inheritance hierarchy is provided. Functions which are unique, overridden and/or have contributions in different classes of the hierarchy are visually distinguished (e.g., by distinguishing marks). Classes in the hierarchy are graphically depicted with relative sizes based on percent contribution.

Hierarchical functional and variable composition diagramming of a programming class

Indicating hierarchy diversion in a class diagram. A class inheritance structure for at least one parent class contained in computer program code can be identified to determine a class hierarchy corresponding to the parent class. For at least one child class in the class hierarchy that is a child of the parent class, a parent-child similarity value corresponding to a parent-child diversion of the child class from the parent class can be calculated via a processor. The class diagram can be generated. The class diagram can indicate at least the parent class, the child class and the parent-child similarity value. The class diagram can be presented.

Growing community of inventors

Bengaluru, India

Sarika Sinha