John A. Interrante and Mark A. Linton. Run-time Access to Type Information in C++. In Proceedings of the USENIX C++ Conference, pages 233--240, San Francisco, California, April 1990.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....6 conventions. Class The presence of classes as objects at run time can simplify software development, enable dynamic extensions, and enhance debugging facilities. Class is a concrete reifying class that reifies C classes as objects in Choices. Classes are similar to the Dossiers described in [7], but extended to support dynamic code linking and portable debugging. At run time, every Object in the Choices system refers to a specific Class. These Objects have the reflective computation functions isMemberOf and isKindOf to test whether they belong to particular classes or hierarchies. Class ....

John A. Interrante and Mark A. Linton. Run-time Access to Type Information in C++. In Proceedings of the USENIX C++ Conference, pages 233--240, San Francisco, California, April 1990.

....type as a string. To offer this functionality, all classes must be derived from a distinguished base class Object, and class implementors must manually provide the information used by the run time mechanism. The ET user interface framework [1] provides similar capabilities. Interrante and Linton [14] propose a Dossier class as a standard interface for class information; the functionality provided by this interface subsumes the functionality of typecodes. Interrante and Linton propose extending the language to generate a virtual function automatically for each class that returns an appropriate ....

John A. Interrante and Mark A. Linton. Runtime access to type information in C++. In Usenix C++ Conference Proceedings, pages 233--240, Berkeley, CA, 1990. Usenix Association.

....run time overheads for manipulating smart pointers. In addition, Edelson s precompiler is quite similar to a preprocessor because it needs to parse type definitions from the source code, and hence is susceptible to the same problems we described earlier for preprocessors. Interrante and Linton [IL90] proposed a Dossier class as a standard interface for runtime type information in C . A (preprocessor style) dossier generator is used to create Dossier objects from the source code. Interrante and Linton propose that the language be extended to automatically generate a virtual function for each ....

....huge gap in performance about five orders of magnitude between main memory latencies and disk latencies. A cost effective approach to bridge this gap is to introduce a new level into the memory hierarchy. Compressed in memory storage uses part of main memory as a cache for compressed pages [Wil90, WLM91, Wil91, AL91, Dou93] this divides the main memory into partitions for uncompressed pages and compressed pages. The use of compressed in memory storage can improve overall system performance because paging from the compression cache may be faster than paging from disk. The performance ....

John A. Interrante and Mark A. Linton. Run-Time Access to Type Information in C++. In USENIX C++ Conference, Berkeley, California, 1990. USENIX Association. 196

....system. Classes provide run time type information, enabling the querying of class inheritance and class instance relations among objects. Instruments that are related by inheritance can be controlled in groups dynamically. However, the instrument selection is purely based on class type information[10]. This introspection scheme does not go beyond the class level, nor does it explicitly represent relations among instruments other than Classes. A similar class based approach is adopted by De Pauw et al. 19] Snodgrass[25] presents a method for monitoring program execution in which a programmer ....

J. A. Interrante and M. A. Linton. Run-time Access to Type Information in C++. In Proceedings of the USENIX C++ Conference, San Francisco, California, April 1990.

....system. Classes provide run time type information, enabling the querying of class inheritance and instance relations on the fly. Instruments that are related by inheritance can be controlled in groups dynamically. However, the instrument selection is purely based on class type information[IL90] This introspection scheme does not go beyond the class level, nor does it explicitly represent relations among instruments other than Classes. De Pauw et al. PHKV93] adopt a similar class based approach. Some researchers have looked into how to organize instrumentation data rather than the ....

John A. Interrante and Mark A. Linton. Run-time Access to Type Information in C++. In Proceedings of the USENIX C++ Conference, pages 233--240, San Francisco, California, April 1990.

....at compile time (or link time) at the expense of full portability we must rely on debugging information and knowledge of the linking process. Preprocessors for run time type description have also been proposed (e.g. Ede92a] The best known is Interrante and Linton s dossier system [IL90] where a preprocessor style dossier generator is used to create Dossier objects from the source code. Interrante and Linton also proposed that the language be extended to automatically generate a virtual function for each class to access the corresponding dossier object. For reasons described in ....

John A. Interrante and Mark A. Linton. Run-Time Access to Type Information in C++. In USENIX C++ Conference, Berkeley, California, 1990. USENIX Association.

....loading and linking of the appropriate code. 70 8.2 Type Descriptors and Dossiers Type descriptors provide useful information about types at runtime to an object manipulation system. The term dossier was coined by J. Interrante and M. Linton in their work on runtime type information for C [16] and is synonymous with type descriptor. Two research efforts that generate type descriptors for use in support of persistent objects are: a system developed at the University of Utah (in which the author participated) 21] and work done at the University of Texas [28] ffl A Dossier Driven ....

....object files. These descriptors give the size of data types and the location of pointers within these types. The output of this preprocessor can then be linked into the application to provide run time type information. ffl Runtime Access to Type Information in C , J. Interrante and M. Linton, 1990 [16] 71 This paper proposes a Dossier class as a standard interface for accessing type information from within a C program. It advocates the addition of a predefined member in all classes to provide this information. The definition of this class is as follows: class Dossier public: Dossier ( ....

Interrante, J. A., and Linton, M. A. Runtime access to type information in C++. In USENIX Proceedings C++ Conference (1990), USENIX Association, pp. 233--240.

....function tables, and (vi) programmer declaration of supporting functions and observance of programming style restrictions. We describe a new approach which poses no constraints in (i) v) and minor client obligations in (vi) Our approach is based on preprocessor generated dossier objects[13], which drive fully polymorphic (i.e. applicable to all types) load and store functions. In addition to supporting object persistence, our approach provides a fully general means for transporting object graphs in address space independent form (i.e. pickled , with unswizzled pointers) Our ....

John A. Interrante and Mark A. Linton. Runtime access to type information in C++. In USENIX Proceedings C++ Conference, pages 233--240. USENIX Association, 1990.

....function tables, and (vi) programmer declaration of supporting functions and observance of programming style restrictions. We describe a new approach which poses no constraints in (i) v) and minor client obligations in (vi) Our approach is based on preprocessor generated dossier objects[14], which drive fully polymorphic (i.e. applicable to all types) load and store functions. In addition to supporting object persistence, our approach provides a fully general means for transporting object graphs in address space independent form (i.e. pickled , with unswizzled pointers) Our ....

John A. Interrante and Mark A. Linton. Runtime access to type information in C++. In USENIX Proceedings C++ Conference, pages 233--240. USENIX Association, 1990.

....Within OMOS we have fragments (compiler emitted object files) OMOS meta objects, cached modules (constructed from meta objects) and miscellaneous state information. For applications in a particular O O language, we may have persistent class instances, class description objects (e.g. C dossiers [IL90], see x5) and class implementation modules. Two fundamental design questions arise concerning persistence in this diverse world of objects: 1. To what extent should these varieties of objects be treated uniformly or differentially, and 2. Where should modules physically reside Our position on the ....

John A. Interrante and Mark A. Linton. Runtime access to type information in C++. In USENIX Proceedings C++ Conference, pages 233--240. USENIX Association, 1990.

No context found.

IL90 John A. Interrante and Mark A. Linton. "Run-Time Access to Type Information in C++." USENIX, Conference Proceedings 1990. 233-240.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC