792 results about "Source code file" patented technology

A method and apparatus to create an intermediate language or source code file from a server-side resource or dynamic web page file. The source code can then be compiled into an executable class allowing for rapid generation of web page control objects that perform server-side functions, including the rendering of client responses. The code generation scheme of the present invention is capable of creating control objects connected in a hierarchy to handle event processing and the setting of attributes to the specific objects.

A software system is disclosed which facilitates the process of tracing the execution paths of a program, called the client. The tracing is performed without requiring modifications to the executable or source code files of the client. Trace data collected during the tracing operation is collected according to instructions in a trace options file. At run time, the tracing library attaches to the memory image of the client. The tracing library is configured to monitor execution of the client and to collect trace data, based on selections in the trace options file. Conditional tracing, through the use of triggers and actions taken in response to the triggers, allows the developer to control the tracing operation. The triggers can be conditional triggers in which the corresponding action is taken only if a conditional expression is satisfied. The system can trace multiple threads and multiple processes. The tracing system provides a remote mode and an online mode. In remote mode, the developer sends the trace control information (which can include triggers and corresponding actions) to a remote user site together with a small executable image called the agent that enables a remote customer, to generate a trace file that represents execution of the client application at the remote site. In online mode, the developer can generate trace options (including triggers and corresponding actions), run and trace the client, and display the trace results in near real-time on the display screen during execution of the client program.

A process and system for entering and retrieving previously stored data at a client computer in an HTML form accessed from an intra- or internet source. A set of data in a form file is provided in a program storage device accessible by the client computer. The form file further contains information concerning time of creation of the data and a unique identification which distinguishes the form file from other forms. A blank form is then accessed from an intra- or internet source and viewed on the client computer. The form file is then accessed from the program storage device and data from the form file is utilized to complete the blank form and the completed form is transmitted to the intra- or internet source. Each form file may be stored as an HTML source file combined with a set of data for the source file, and the program storage device includes a combined form table containing a list of the form files. Alternatively, the form file includes a plurality of sets of data, the sets of data being for a plurality of HTML source files previously accessed, and the program storage device further includes a separate form table containing a list of HTML source files previously accessed from the intra- or internet source.

A method of generating a parser of a source code file that references a syntactic dictionary, a method of compressing the file, and apparatuses that use the methods. The syntactic dictionary is converted into a corresponding plurality of expressions, of a context-free grammar, that are a grammar of the source code. The parser is constructed from the expressions. The source code is compressed using the parser. Preferably, the grammar of the source code file is a D-grammar and the expressions are regular expressions. Preferably, the parser is a deterministic pushdown transducer. An important case of the present invention is that in which the source code is XML code and the syntactic dictionary is the document type declaration of the XML code. Apparatuses that use a parser of the present invention include compressors, decompressors, validators, converters, editors, network devices and end-user / hand-held devices.

Provided is a method, system, and program for enabling analysis of proposed changes to program statements in a source code file. A data structure is generated indicating a plurality of program statements affected by one of a plurality of selected program statements to change, wherein the data structure indicates a hierarchical relationship of the effect of program statements on one another resulting from changes to the selected program statements. The data structure is provided to a software development tool to enable a programmer to display information on the hierarchical relationship of the affect of the program statements on one another resulting from changes to the selected program statements.

A Source Code Author Identifier (SCAI) automates the process of manually running a comparison to identify changes between versions of a source code file and associates identified changes with the author who made the change. After a developer identifies a segment of code in a first file, wherein the first file as a newer version of a second file, SCAI compares the segment of code in the first file to a corresponding segment of code in the second file. SCAI identifies the author of the first file whenever a difference is detected between the segment of code in the first file and the corresponding segment of code in the second file. SCAI displays the author of the first file next to the detected difference between the segment of code from the first file and the corresponding segment of code from the second file. SCAI can repeat the comparison across a plurality of versions of the file, comparing each version with the previously created version.

The invention provides a technique for managing multiple contextual views of source code files. In a file system, different tasks demand that source code files be grouped in different hierarchical directories. When some or all of this manipulation is of the physical files themselves, the directories can become confused, and it may be difficult for the next user to access needed source code files. In the technique of the invention, the physical location of the files is independent of all contextual views, and is maintained in a separate viewable hierarchy. All items in contextual view hierarchies contain only references to the physical location of the source code files, and so modifications of those items, such as delete, move and copy, only alter the references themselves. A separate set of operations can be used for explicitly maintaining or modifying the physical source code files.

The invention discloses a testing method based on software defect mode, comprising the steps of: reading source code files of programs to be tested and SDSM description file of a defect state machine, carrying out pre-processing of the programs to be tested, analyzing the SDSM description file; carrying out lexical analysis and grammar analysis of the programs to be tested and constructing abstract syntax tree; generating a control flow graph and a symbol table according to the abstract syntax tree and carrying out the calculating and updating of variable value interval sets according to the control flow graph and the symbol table; carrying out function invoking relation analysis of the programs to be tested and generating a function invoking relation graph; searching the control flow graph by taking the function as unit according to the function invoking relation graph, calculating the state migration of each node defect state machine on the control flow graph, and reporting corresponding checking point when the defect state machine enters the defect state. The invention also discloses a testing system based on software defect mode, which comprises an input module, a defect mode uniformity testing frame and a user interface module and completes the uniform test on the programs to be tested.

A software system is disclosed which facilitates the process of tracing the execution paths of a program, called the client. The tracing is performed without requiring modifications to the executable or source code files of the client. Trace data collected during the tracing operation is collected according to instructions in a trace options file. At run time, the tracing library attaches to the memory image of the client. The tracing library is configured to monitor execution of the client and to collect trace data, based on selections in the trace options file. Conditional tracing, through the use of triggers and actions taken in response to the triggers, allows the developer to control the tracing operation. The triggers can be conditional triggers in which the corresponding action is taken only if a conditional expression is satisfied. The system can trace multiple threads and multiple processes. The tracing system provides a remote mode and an online mode. In remote mode, the developer sends the trace control information (which can include triggers and corresponding actions) to a remote user site together with a small executable image called the agent that enables a remote customer, to generate a trace file that represents execution of the client application at the remote site. In online mode, the developer can generate trace options (including triggers and corresponding actions), run and trace the client, and display the trace results in near real-time on the display screen during execution of the client program.

Systems and methods are provided for performing static error analysis on source code. A computer system having an operating system may contain a number of source code files. During a normal build process, a build program may be used to set various compilation options and to invoke appropriate compilers that compile the source code files into executable code. Static analysis debugging tools may be used to perform static analysis on the source code files. The appropriate static analysis tools may be invoked using a static analysis tool management program. Directory, path and name modification may be used to invoke the analysis tools. A monitoring program may be used to determine how to invoke the tools. The operating system may be modified so that the static analysis tools are invoked in place of the compilers when the build program is run.

The present invention provides a system and method for managing source code. The system comprises an administrative module including a build services module configured to perform a build action on a source code file and a library module functionally coupled to the administration module and configured to support library services operations on the source code file. The method comprises the steps of managing a source code file with a document management based library module configured to perform a file action on a folder, and managing a source code project, associated with the source code file, with an administrative module.

Plagiarism of software source code is a serious problem in two distinct areas of endeavor-cheating by students at schools and intellectual property theft at corporations. A number of algorithms have been implemented to check source code files for plagiarism, each with their strengths and weaknesses. This invention consists of a combination of algorithms in a single software program to assist a human expert in finding plagiarized code.

A system for generating target language source code utilizing an object oriented code generator is disclosed. A desired computer programming function is specified using a fourth generation language. An object oriented converter converts the fourth generation language specification into an object oriented model which retains the function and inter-relationships defined in the specification. The object oriented model is applied against a set of source code templates for a desired target language, which will typically be a third generation language. An object oriented generator engine parses the resulting collection of templates to form source code files having the desired programming function in the desired target language.

A computer implemented method and computer usable program product for version control of source code. In one embodiment, a source code file is scanned for relationships between source code sections. A semantic graph with dependencies and metadata describing the source code sections is constructed. The dependencies indicate the relationships between the source code sections. If changes are received for the semantic graph, the semantic graph is modified with the changes to form a modified semantic graph.

A method, system and computer program product for creating a software product in an Integrated Development Environment (IDE). In one embodiment, remote object status data is received by a software development module which may be a source code editor or a program execution emulator. Responsive to the received data, the remote object status is rendered within a display medium of the software development module by decorating or otherwise distinguishing the remote OIDs in the IDE. In one embodiment in which the software development module is a source code editor, the method further includes detecting a remote object identifier in a source code file processed by the source code editor, and in response thereto, displaying the remote object status within the source code editor.

A source code control architecture. A client user checks out a copy of a source code file to the client using a file checkout process. A client cache maintains a pristine copy of the file, and a client activity list maintains a list of commands executed during the offline mode to effect modifications to the copy. The client cache contains a pristine copy of all source code files that are modified or deleted in a local client workspace. The cache is maintained whether the user is online or offline. When the user is offline, the cache is utilized to facilitate many of the activities that historically would require server connectivity. The command activity list allows a developer to continue changing the source code while offline by automatically recording the executed commands. The offline commands are reconciled to the server, and used to update the server file(s) when the client returns online.

Embodiments of the present invention provide a method, system and computer program product for the automated suggestion of code usage patterns in an IDE. In an embodiment of the invention, a method for automated suggestion of code usage patterns in an IDE is provided. The method includes receiving input of a code snippet for a source code file of a software development project loaded into memory of a host computer for display through an IDE. The method further includes matching terms of the received input to terms in different blocks of code in different source code files of the software development project. The method yet further includes selecting one of the different blocks of code as a code completion choice for insertion into the source code file in the IDE. Finally, the method includes inserting the selected one of the different blocks of code into the source code file in the IDE.

Provided is a method, system, and program for enabling analysis of proposed changes to program statements in a source code file. A data structure is generated indicating a plurality of program statements affected by one of a plurality of selected program statements to change, wherein the data structure indicates a hierarchical relationship of the effect of program statements on one another resulting from changes to the selected program statements. The data structure is provided to a software development tool to enable a programmer to display information on the hierarchical relationship of the affect of the program statements on one another resulting from changes to the selected program statements.

This invention provides a method and system for debugging hybrid source code such as JavaServer Pages (JSP) code. The method comprises the steps of running a server within a virtual machine instance; reading a hybrid source code file into a page compiler and compiling the hybrid source code to produce a servlet source code; intercepting and loading the servlet source code into a debugger, before execution by the Web server. Using an HTML browser as client to the Web server which in turn is running in the development environment to thereby debug the JSP code in real-time. In a preferred embodiment, the load class in the page compiler is replaced to redirect the compiled source to the debugger.

A software tool is provided to analyze static source code. Source Code files are selected to define the project work space. A class and a method in the class are selected from said selected source code files. The tool generates a Call Tree as an ordered recursive sequence of all method calls in different classes or their instances that are invoked by said selected method in said selected class. A Sequence Diagram is generated from said Call Tree. The tool remembers all updates to the Call Tree used to generate the Sequence Diagram. This information is used when a generated Sequence Diagram is impacted due to changes made to any source code file included in the project.

A method and apparatus for converting programs and source code files written in a programming language to equivalent markup language files is provided. The conversion may be accomplished by a static process or by a dynamic process. In a static process, a programming source code file is converted by an application to a markup language file. A document type definition file for a markup language is parsed; a source code statement from a source code file is parsed; an element defined in the document type definition file is selected based on an association between the element and an identifier of a routine in the source code statement; and the selected element is written to a markup language file. In a dynamic process, the program is executed to generate the markup language file that corresponds to the source code file or presentation steps of the program. The application program is executed; a document type definition file for a markup language is provided as input; an element defined in the document type definition file is selected based on a routine called by the application program; and the selected element is written to a markup language file.

Various embodiments of a system and method for generating software documentation are disclosed. A software documentation generator may input a variety of information sources. In one embodiment, these information sources may include various types of files such as application source code files, tag library files, tag library descriptors (TLD), library source code, web services description language (WSDL) files, configuration files, defect reports, and text files. The software documentation generator may analyze each source to determine its type and use this information to extract documentation data from the source according to the format of the data included in that source. The software documentation generator may reformat the documentation data extracted from each source into a uniform format and aggregate the uniformly formatted data into a uniformly formatted aggregate input document. The software documentation generator may transform this document into one or more sets of software documentation in a specified format.

The embodiment of the invention discloses a detection analysis method and device for static code defects. The problem that the existing code defect detection analysis of a to-be-detected source code file is low in efficiency is solved. The detection analysis method includes the steps that a to-be-detected source code file is obtained, wherein the to-be-detected source code file comprises test units of a plurality of to-be-detected source code file sections; according to the to-be-detected source code file, an abstract syntax tree is generated; according to the abstract syntax tree, correlations between all present test units and other test units are set, and the correlated dependency relationships between all the present test units and the other test units are obtained, wherein the other test units are the other test units except for the present test unit in the multiple test units; according to the dependency relationships, serial detection analysis and parallel detection analysis are combined, code defects of the to-be-detected source code file are detected and analyzed, and the detection analysis efficiency of the code defects of the to-be-detected source code file is improved.

Methods and systems are provided for generating source code from XML formatted device data sheets. Information is accepted from a user regarding whether data definitions, string tables and / or link tables are needed in a software project. Files are created corresponding to the data definitions, string tables and / or link tables. The files are then collected and compiled into resultant source code. An application generator performs the compilation of the input files into source code. The resultant source code may be incorporated into a software development project and may be updated when needed.

Provided is a method, system, and program for performing an impact analysis of program statements in a source code file, wherein each program statement has at least one of an input parameter and output parameter. A selection is received of at least one program statement in the source code file. For each selected program statement, a determination is made of program statements in the source code file having as one input parameter one program artifact that is affected by the selected program statement.

A method, system, and data structure for incorporating random instrumentation logic within a simulation model. The data structure of the present invention includes a first field containing data representing an assigned target and a second field containing data representing a logic value to be assigned to the assigned target. The first field and the second field are incorporated within a comment line of a design target entity source code file. A pre-pended comment identifier field identifies the data structure as a hardware description language comment.

The embodiment of the invention discloses a smart contract execution method and device, equipment and a medium. The method comprises the steps of obtaining a transaction request initiated based on a smart contract; in the process of executing the smart contract to process the transaction request, calling a contract dynamic link library file, wherein an intelligent contract bytecode file is decompiled into a target advanced language to obtain a contract source code file, and the contract source code file is compiled to obtain the contract dynamic link library file. Through the technical schemeprovided by the embodiment of the invention, the execution efficiency of the smart contract can be improved.

The invention discloses a multi-channel method and a system for issuing software. By the aid of the method, a plurality of channel numbers are set in accordance with a plurality of issuing channels of the software, every channel number represents a software issuing channel, corresponding compiled configuration files are generated in accordance with all channel numbers, a plurality of channel packages are generated in accordance with all compiled configuration files and source code files of the software, channel packages contain channel numbers, and channel packages serve as issuing packages and are issued on corresponding software issuing channels. The system comprises a channel configuration device, a software compiling device and an issuing server, and the channel configuration device, the software compiling device and the issuing server are used for achieving functions. The invention also discloses a process for testing the software before the software is issued normally and a corresponding testing server. Channel numbers are added to the software, the software can be followed and products can be improved.

A computer implemented method and apparatus for mobile application development comprises receiving at least one compiled source code file into the temporary sandbox; and testing the at least one compiled source code file in the temporary sandbox.

A method, non-transitory computer readable medium, and apparatus that obtains a version history for a plurality of source code files associated with the computer program. At least one defect probability value is generated for each of the plurality of source code files using at least one metric and the obtained version history. One or more of the plurality of source code files having a higher risk of including one or more defects than one or more other of the plurality of source code files are identified based on the generated defect probability values. Information regarding each of the one or more identified source code files is output.