Browse Prior Art Database

Programming development support by automatic expansion of registered codes related to specific module call to editor Disclosure Number: IPCOM000033754D
Original Publication Date: 2004-Dec-28
Included in the Prior Art Database: 2004-Dec-28
Document File: 2 page(s) / 12K

Publishing Venue



Disclosed is a programming standardization support system which automatically inserts predefined codes when registered modules are loaded to editors. This system aims to force users to obey rules of implementing preprocessing and postprocessing logic, which are often stated in standardization guidelines.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 2

Programming development support by automatic expansion of registered codes related to specific module call to editor

In software development projects, it is common to set coding rule standards to force members to implement preprocessing and postprocessing logic for specific module calls. (Here, a "module" may be a method for Java or function for C).

But it is difficult to force users to obey these standards, and checking for codes which violates these rules takes a great amount of time and workload.

The programming development environment to solve this problem is described below.

1. At first, a module call and corresponding processing (preprocessing and postprecessing
) are

registered to this system.

(It is called "module data" in this document)
2. When user loads a registered module onto an editor, the system inserts preprocessing and post processing codes automatically.

Here, the expression "load a registered module" represents two operations; (a) When user types this module name dynamically on editor.

(b) When user choose this module name from a list of modules names.

(Most of programming development environment provides the function which

chooses a module name from list and is made to reflect in an editor.)
3. The system inserts preprocessing code to the front of module call.
4. The system loads module call to the editor.
5. The system inserts postprocessing code to the behind of module call.

The system can expand multiple postprocessing which is correlated with the return value of a module call to editor.

Figure 1 shows the module data structure.

For example, the first line means th...