ACM Home Page
Please provide us with feedback. Feedback
Towards a formalization for COM part i: the primitive calculus
Full text PdfPdf (150 KB)
Source Conference on Object Oriented Programming Systems Languages and Applications archive
Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications table of contents
Seattle, Washington, USA
SESSION: Foundations table of contents
Pages: 331 - 342  
Year of Publication: 2002
ISBN:1-58113-471-1
Also published in ...
Author
Riccardo Pucella  Cornell University, Ithaca, NY
Sponsors
ACM: Association for Computing Machinery
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 25,   Citation Count: 3
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/582419.582449
What is a DOI?

ABSTRACT

We introduce in this paper a typed calculus intended to capture the execution model of COM. The innovation of this calculus is to model very low-level aspects of the COM framework, specifically the notion of interface pointers. This is handled by specifying an allocation semantics for the calculus, thereby modeling heap allocation of interfaces explicitly. Having an explicit way of talking about interface pointers allows us to model in a reasonable way the notions of interface sharing and object identity. We introduce a type system that can be used to disambiguate between specification and implementation of interfaces. The type system moreover can capture a notion of COM conformance, that is, the legality of COM components. We discuss extensions of the calculus to handle subtyping of interfaces, dynamic interface negotiation and aggregation.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
R. Ibrahim and C. Szyperski. Can Component Object Model (COM) be formalized? --- the formal semantics of the COMEL language. Work-In-Progress, IRW/FMP'98. Also appears as Technical Report TR-CS-98-09, The Australian National University, 1998.
 
4
Microsoft Corporation and Digital Equipment Corporation. The Component Object Model Specification. Draft version 0.9, available from http://www.microsoft.com/com, 1995.
5
 
6
 
7
 
8
R. Reussner. Dynamic types for software components. In Companion of the Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA '99), 1999.
 
9
R. Reussner and D. Heuzeroth. A Meta-Protocol and Type system for the Dynamic Coupling of Binary Components. In Proceedings of the OOPSLA'99 Workshop on Object Oriented Reflection and Software Engineering, 1999.
 
10
 
11
 
12
 
13
 
14
 
15
 
16
C. Szyperski. Component Software. Addison Wesley, 1997.
 
17
 
18