Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Independent Class/Application Relationship in OO Environment

IP.com Disclosure Number: IPCOM000116334D
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Related People

Aoki, J: AUTHOR

Abstract

Disclosed is a technique to achieve independent relationship between class and application. Using this technique, the application's recompile and relink is not necessary although class data member and/or member function is changed.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 89% of the total text.

Independent Class/Application Relationship in OO Environment

      Disclosed is a technique to achieve independent relationship
between class and application.  Using this technique, the
application's recompile and relink is not necessary although class
data member and/or member function is changed.

      The Figure shows the technique to cope with class data member
change.  This is achieved by not statically generating class instance
in application (this is conventional way to generate instance) but
generating it through user defined constructor.  If the instance is
statically generated in application, the class information, which
might not be the latest, is used.  That information is not latest if
data member change happened after application's compilation time.
The benefit of using user defined constructor is that, only
re-compiling/re-linking the constructor (not application) makes it
possible for application to use the latest class information through
constructor even if class' data member is changed.  Note that for
C++*, user defined constructor needs to be defined in another class
(in this example, new_person() in class factory) because C++ does not
support meta class mechanism.

      The Figure also shows conventional technique for avoiding
re-compile/re-link when class' member function (in this example,
speak() in class person) is changed.  This is done by providing
member function as DLL.

      This technique is very general and can be appl...