Skip Navigation

The Computer Journal 2000 43(6):512-523; doi:10.1093/comjnl/43.6.512
© 2000 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Cho, E.-S.
Right arrow Articles by Kim, H.-J.
Right arrow Search for Related Content
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Interface/implementation Separation Mechanism for Integrating Object-oriented Management Systems and General-purpose Programming Languages

Eun-Sun Cho1 and Hyoung-Joo Kim2

1 Graduate School of Information and Communication, Ajou University, Suwon, 442-749, Korea Email: eschough@madang.ajou.ac.kr 2 Department of Computer Science, Seoul National University, Seoul 151-742, Korea

When a database is shared in different database applications, it is helpful for data-independence and program readability to screen off the implementation details of a schema class from the programs other than the method implementation code. This makes some systems allow their users to define the schema class in two parts—the interface and the implementation. In this paper, we propose a preprocessing-based approach with the object model for OODBPLs (object oriented database programming languages) with interface/implementation separation.


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.