yms@cis.ufl.edu (Yuh-Ming Shyy) (05/18/91)
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 ==================================================================
davidm@uunet.UU.NET (David S. Masterson) (05/20/91)
>>>>> On 18 May 91 14:31:11 GMT, yms@cis.ufl.edu (Yuh-Ming Shyy) said:
yms> We are developing an OODB to support the whole lifecycle of the
yms> development of complex software systems. We are trying to treat "methods"
yms> also as "objects" (as instances of a system-defined class called
yms> "METHOD") and store them uniformly in the database. Under our current
yms> implementation, methods are written in our own database programming
yms> language called K and will be translated into C++ code and get executed
yms> through a Sun C++ 2.0 compiler. The problem is that how to handle the
yms> resulting xxx.o files in the context of an object-oriented database? Just
yms> modeling "files" as another object class seems not a good solution since
yms> these xxx.o files are treated as dynamically-paged files under Sun
yms> operating system and therefore it is difficult to actually "store" them
yms> in the OODB. We would like to know if there is anyone thinking about
yms> the same problem or has come out with some neat solution? Any comment
yms> will be highly appreciated. Thanks.
Why treat the results of the C++ compiler as anything in the object system?
Isn't it hidden under the database interface? Just treat it as an external
object of "void" type...
--
====================================================================
David Masterson Consilium, Inc.
(415) 691-6311 640 Clyde Ct.
uunet!cimshop!davidm Mtn. View, CA 94043
====================================================================
"If someone thinks they know what I said, then I didn't say it!"