Issue 2090:  Mapping of Object, Serializable and Externalizable (java2idl-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: The proposal here is to map Object, Serializable and Externalizable
 to distinct entities, rather than just to an any.
 
 These entities are
 module java {
     module lang {
        typedef any _Object;
     };
     module io {
         typedef any Serializable;
         typedef any Externalizable;
     };
 };
 
 and so
 java.lang.Object will map to ::java::lang::_Object,
 java.io.Serializable will map to ::java::io::Serializable, and
 java.io.Externalizable will map to ::java::io.Externalizable
 

Resolution: 
Revised Text: 
Actions taken:
October 16, 1998: received issue
February 23, 1999: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <nash@hursley.ibm.com>
Date: Fri, 16 Oct 1998 17:59:19 +0100
From: Simon Nash <nash@hursley.ibm.com>
Organization: IBM
To: issues@omg.org
CC: java2idl-rtf@omg.org
Subject: Mapping of Object, Serializable and Externalizable

The following Java to IDL issue was raised by Vijay Natarajan.
It needs to be added to the issues database.

The proposal here is to map Object, Serializable and Externalizable
to distinct entities, rather than just to an any.

These entities are
module java {
    module lang {
       typedef any _Object;
    };
    module io {
        typedef any Serializable;
        typedef any Externalizable;
    };
};

and so
java.lang.Object will map to ::java::lang::_Object,
java.io.Serializable will map to ::java::io::Serializable, and
java.io.Externalizable will map to ::java::io.Externalizable

These definitions could either be treated as builtins by the compiler
or have preprocessor guards to prevent them from being processed more
than once.

   Simon
-- 
Simon C Nash, IBM Java Technology Centre, Hursley, UK
MailPoint 146, x245156  Tel. 01962 815156 or +44-1962-815156
Internet: nash@hursley.ibm.com  Notes mail: Simon Nash@ibmgb