Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!uflorida!reef.cis.ufl.edu!yms
From: yms@cis.ufl.edu (Yuh-Ming Shyy)
Newsgroups: comp.lang.c++
Subject: Modeling files as object class in OODB
Message-ID: <28597@uflorida.cis.ufl.EDU>
Date: 18 May 91 14:36:57 GMT
Sender: news@uflorida.cis.ufl.EDU
Organization: UF CIS Dept.
Lines: 23
Originator: yms@reef.cis.ufl.edu

We are developing an OODB to support the whole lifecycle  of  the
development  of  complex software systems. We are trying to treat
"methods" also as "objects" (as  instances  of  a  system-defined
class  called "METHOD") and store them uniformly in the database.
Under our current implementation, methods are written in our  own
database  programming  language  called  K and will be translated
into C++ code and get executed through a Sun  C++  2.0  compiler.
The  problem  is  that how to handle the resulting xxx.o files in
the context of an object-oriented database? Just modeling "files"
as  another  object  class  seems not a good solution since these
xxx.o files are treated  as  dynamically-paged  files  under  Sun
operating  system  and  therefore  it  is  difficult  to actually
"store" them in the OODB. We would like to know if there is  any-
one  thinking  about  the  same problem or has come out with some
neat solution? Any comment will be highly appreciated. Thanks.

=================================================================
Yuh-Ming Shyy 
Database Systems R&D Center 
University of Florida

email: yms@reef.cis.ufl.edu
==================================================================