Path: utzoo!attcan!telly!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!rex!uflorida!yms@cis.ufl.edu From: yms@cis.ufl.edu (Yuh-Ming Shyy) Newsgroups: comp.object Subject: Treat Type and Method as First-class Object Message-ID: <27061@uflorida.cis.ufl.EDU> Date: 21 Feb 91 21:32:13 GMT Sender: news@uflorida.cis.ufl.EDU Organization: UF CIS Dept. Lines: 19 Many works have been done in applying object-oriented database technology to software engineering. Currently I am also taking a similar approach to a DBMS-support software environment where we treat everything as objects. The problem is that if we treat type and method uniformly as first-class objects and store them in the database (as instances of class "TYPE" and "METHOD"), then the traditional programming style (using files) does not fit because information will be redundantly stored in both files and data- base, and each time the .h file is executed, how to handle those types and methods objects which have already been stored in the database from the previous execution? On the other hand, if we distribute these information as database objects without using files, then there is a problem if we want to execute the system using a persistent C++ (such as ODE and E). Any comment will be highly appreciated. Thanks. yms@reef.cis.ufl.edu Brought to you by Super Global Mega Corp .com