Browse Prior Art Database

Method and apparatus to identify code changes required in multiple components

IP.com Disclosure Number: IPCOM000190455D
Original Publication Date: 2009-Nov-30
Included in the Prior Art Database: 2009-Nov-30
Document File: 2 page(s) / 20K

Publishing Venue

IBM

Abstract

Disclosed is an idea that would help code developers to communicate the changes that were required in different parts of code in the same component or different component when code at one place was modified. The workaround is to write comments in the code (at multiple places thus multiple times) explaining what should be modified in other parts of the code. There is no current existing complete solution that would force the modifications that are required in other parts of the code.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Method and apparatus to identify code changes required in multiple components

A program is disclosed that would help code developers to communicate the changes that were required in different parts of code in the same component or different component when code at one place was modified.

After the code was initially developed by developers, the code should be maintained over long period. It is quite general that the code should be modified at different places while maintaining the code. However the code could be large number of files in a component and many components could be involved. It becomes tough in this case to identify the dependants of the code change that was made in a file.

A program is proposed that would use tags with names around all the code in different files/components. The code that needs to be modified at different places based on changes at a place in code would have unique tag name. The tags will help the code maintainer to figure out the code changes that are to be done in different components when he runs compiler on it (compiler should be enhanced to support this feature) which is not possible with mere comments in the code. If dependant code changes are present in different components, information about these tags in these components should be included in the design document while initially designing the code. The header file will consist of all the tags in the respective subcomponent. If the changes are required across different sub components, the header file in each component will have the tag name but with "extern" prepended to it. If the code changes are needed across the components, the same tag would be used across the components and the header fil...