Issue 1529:  DynAny::get_value collision (obv-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: OBV specifies a DynAny::get_value operation to retrieve a value from a
 DynAny, but this operation breaks the existing DynFixed::get_value
 operation. I suggest renaming the DynAny::get_value to avoid the collision
 (gee, if we didn"t use "value" as one of those funny keyword identifiers,
 this wouldn"t be a problem).
 

Resolution: :get_value
Revised Text: :get_value to avoid the collision
Actions taken:
June 18, 1998: received issue
July 30, 1998: closed issue
Discussion: 
 rename methods to get_val. Accepted for CORBA 2.3
End of Annotations:=====
Return-Path: <nash@sp3at21.hursley.ibm.com>
Date: Thu, 18 Jun 1998 00:24:44 +0100
From: Simon Nash <nash@hursley.ibm.com>
Reply-To: nash@hursley.ibm.com
Organization: IBM
To: obv-rtf@omg.org, issues@omg.org
Subject: TypeCode issues

I received some questions from the IBM implementers of the new ORB
operations for TypeCodes defined in section 5.8.2.
 
3) The new TypeCode kinds involved are:
      tk_value created via "create_value_tc"
      tk_value_box created via "create_box_value_tc"

   In the second case, shouldn't the TypeCode kind
   and the TypeCode API nomenclature be the same
   (value_box vs. box_value) ?