Issues for Python Mapping 1.2 RTF discussion list

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 5471: In the resolution of issue 4659
Issue 5727: list of operations provided by the ORB object
Issue 5779: OpaqueValue needs to be documented in the Python Language mapping

Issue 5471: In the resolution of issue 4659 (python-ftf)

1. In the resolution of issue.... 


(a) The system exception that is raised is said to be BAD_PARAM. Since
it is a bad context that is being taken exception to, why is the
BAD_CONTEXT exception not used instead?


(b) It is better to also define a standard minor code with an associated
error description when a use of a standard system exception is
specified. This helps the user figure out what caused the system
exception to be triggered. This is missing in the resolution.

In the list of operations provided by the ORB object, the first is list_initial_references(). 

In the CORBA spec, there is no operation by that name in the PIDL, but there is a list_initial_services() operation. 

This looks like a typo

OpaqueValue, a new native type introduced in Issue 2162 (void *
in DII Chapter) for add_arg, was never documented in any of the language
mappings. Language Mapping that claim that the DII interfaces map
according to regular rules need to provide mapping rules for OpaqueValue
and document it. The mapping would simply be OpaqueValue --> (void *) or
equivalent.