Browse Prior Art Database

Determining a Parent List for a Non-Directed Graph, using a Tree

IP.com Disclosure Number: IPCOM000111978D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 49K

Publishing Venue

IBM

Related People

Henshaw, SF: AUTHOR [+2]

Abstract

In a build structure, a user has one or more given outputs on which each has one or more inputs that form that one particular output. For example, we have the following situation: a.exe | ---- a.o | ---- a.c | ---- util.c b.exe | ---- b.o | ---- b.c | ---- util.c

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

Determining a Parent List for a Non-Directed Graph, using a Tree

      In a build structure, a user has one or more given outputs on
which each has one or more inputs that form that one particular
output.  For example, we have the following situation:
          a.exe
             |
              ---- a.o
                      |
                       ---- a.c
                      |
                       ---- util.c
          b.exe
             |
              ---- b.o
                      |
                       ---- b.c
                      |
                       ---- util.c

      In the above case, util.c is the same one file that is included
to make up both a.o and b.o.  This representation would be clearer in
representing  the singularity of the util.c file if a network diagram
were used, but, unfortunately, this diagram view is  not  a  standard
and  pre-provided  view.   Therefore, we need a way of presenting the
fact that util.c is the same one underlying file to the user, using a
tree structure, and allow the user to take action against any one  of
those   "representations"   of   the   one  underlying  file  without
unintentionally damaging the other connections that were made.

      An algorithm is needed by which the program keeps track of  the
parents  of any given node, so that changes to one of those identical
underlying objects does not adversely affect the others.

      For example, in the above case, a user wants to  remove  util.c
from  the  list of files that are used to build b.o.  A user would go
to util.c until b.o and choose some menu action to remove that  file.
Under  the  covers,  when  the  tree  was  being built, the following
structure was created:

                -------------------------------------
                  |  NODE     |     ...