Issue 52: Omission in union C++ mapping
Issue 75: Access to sequence buffers
Issue 91: Efficiency issue in C++ mapping
Issue 92: T__alloc in C mapping
Issue 94: Defining an operator for struct/union/sequence _var types
Issue 95: Re-opening modules
Issue 96: C++ classes for modules
Issue 98: In String Argument Passing Question
Issue 100: Union discriminators in C++
Issue 101: Memory Management Clarification
Issue 123: Fixed structs
Issue 125: Passing of object reference in pointers
Issue 134: Union problem
Issue 141: Practical problem with DII using Request Pseudo Object
Issue 142: inserter and extractor functions for exceptions
Issue 143: Testing exceptions
Issue 144: Rethrowing exceptions
Issue 145: Missing Any inserter
Issue 146: Any extractor signature problem
Issue 147: Defintion of Any
Issue 148: Adding T_copy function
Issue 150: Any string extractor
Issue 154: Problem with Any::to_object memory management
Issue 178: Bounded sequence problem (Section 16.11 p. 16-23)
Issue 185: Return value of maximum() for unbounded sequences
Issue 186: Inconsistent interfaces for the operation pairs *duplicate* and
Issue 187: Freeing inaccessible storage for T_var as out parameter
Issue 188: interface mapping
Issue 189: Distinction between _var and _ptr types
Issue 190: Names of anonymous types
Issue 191: get_principal () needs an environment parameter
Issue 192: Identifier conflicts resulting from the language mapping
Issue 193: Pseudo objects for DSI
Issue 194: Implementation dependency for _var and _ptr
Issue 195: _ptr member accessors for string and objref
Issue 196: illegal union access when discriminator is wrong
Issue 197: TypeCode/Value mismatch in ANY
Issue 198: Representation of void* returned from ANY
Issue 199: Levels of portability conformance requested
Issue 200: fixed- vs. variable-length types
Issue 201: example incorrect?
Issue 202: Assignment to T_var
Issue 203: Detection of initialization of T_var
Issue 204: string and objrev members of constructed types
Issue 205: Taking T out of T_var
Issue 206: Implementation description
Issue 207: C++ mapping complexity
Issue 208: Autoextension of sequences
Issue 209: Sequence implementation
Issue 210: State of release flag for sequence
Issue 211: Sequence maximum() call
Issue 212: References returned from sequence operator[] after realloc
Issue 213: Sequence lacks common features
Issue 214: Sequence buffer types
Issue 215: C vs. C++ coding style
Issue 216: Sequence creation
Issue 217: Copying of out parameters
Issue 218: Semantics of sequence length() operation
Issue 219: Array slice example
Issue 220: Return value of operator[] for array var
Issue 221: Array_forany
Issue 222: Global functions vs. T_var namespace
Issue 223: Storage ownership issue
Issue 224: Pointers vs. values
Issue 225: handling void* from Any
Issue 226: void* from Any for constructed types
Issue 227: anonymus types
Issue 228: callee-allocated storage modification
Issue 229: Typo in table 3?
Issue 230: _var types for fixed-length types
Issue 231: union accessors
Issue 232: Mapping for IDL context
Issue 234: accessor function on SystemException
Issue 235: A_ptr and A_var should be distinct types
Issue 236: operator>>= on strings and object references Allocated storage for out and return strings
Issue 237: Allocated storage for out and return strings
Issue 238: C++ namespaces
Issue 239: Implementation of parameter passing for T_var types
Issue 240: Any and IN_COPY_VALUE
Issue 241: allocbuf and initialization of elements
Issue 242: freebuf and destruction of elements
Issue 244: RTTI vs. _narrow for exceptions
Issue 245: accessor members for structs
Issue 246: Access to sequence elements
Issue 247: TypeCode mapping update for CORBA 2.)
Issue 248: nested ptr and var types
Issue 249: to/from string for Any type safety
Issue 250: union accessors require temporaries
Issue 251: decompose Any into constituent primitives
Issue 252: T_copy for string and array
Issue 253: Name field for SystemExceptions
Issue 254: iterating over Any primitives
Issue 255: Constructor taking discriminant as argument
Issue 256: Accessors for release flag of sequence
Issue 257: Any release flag and operator<<= Accessors for the Any release flag
Issue 258: Accessors for the Any release flag
Issue 259: Accessor for exception id
Issue 260: Exception id for each exception type
Issue 261: TypeCode for each basic and IDL defined types
Issue 262: TypeCode interpreter
Issue 263: buffer classes for sequences
Issue 264: make String_var reference but not adopt
Issue 265: explicit copy/adopt for String_var
Issue 266: operator<< for ostreams and Exceptions ANy release flag and operator
Issue 267: ANy release flag and operator
Issue 268: C++ semantics vs. IDL semantics
Issue 269: Default constructor for String_var
Issue 290: u++ binding for ServerRequest pseudo object
Issue 456: Interpretation of _narrow semantics
Issue 479: DII and DSI are useless with current Any
Issue 480: Persistent Any values
Issue 481: [q] intf name == op name
Issue 482: Defect with anonymus types in union mapping
Issue 484: OMG C++ Mapping: Implicit Conversion Operators
Issue 496: Double underscore identifier mapping
Issue 497: Legal IDL cannot map to C++
Issue 501: Bug in C++ NVList mapping
Issue 594: Boolean type left undefined by C++ mapping
Issue 599: const method qualification should be removed
Issue 600: String_var and Any_var are missing the T_ptr definition
Issue 601: Section 17..13.1 release()method should be added to mappping
Issue 605: Section 8.2: set_exception() supported by BOA?
Issue 608: Interface definition must be standardized
Issue 615: POA_*_tie classes in 18.1.4 can"t be supported
Issue 617: Why does get_principal() take an Environment parameter
Issue 618: IDL from Ennvironment has invalid attribute
Issue 621: C mapping for list_initial_services is incorrect
Issue 622: Section 16.2, Section 16.6: editorial
Issue 627: PortableServer:ObjectId_tow_wstring() and string_to_ObjectId()
Issue 637: Section 18.1.2: _this() and IMPLICIT_ACTIVATION need clarification
Issue 646: Blocking semantics of get_next_response not well specified
Issue 647: include files
Issue 653: sec. 18.1.2: explicit information on _this() is missing
Issue 663: Implementation problem with policy objects using root POA
Issue 673: C++ mapping of servants may result in ambigous run-time behavior
Issue 674: Multiple inheritance of C++ Servants is ill-defined
Issue 678: inout strings modifiable?
Issue 705: C and C++ Mapping question
Issue 721: Bounded strings
Issue 722: Wide string allocation (1)
Issue 723: Wide string allocation (2)
Issue 731: IDL generated C++ types and stream operators
Issue 732: Typo in C++ mapping
Issue 781: C++ mapping for IN object references
Issue 800: Missing Mappings for Object
Issue 801: Alias type codes in any values
Issue 803: C++ mapping: missing from_wchar and to_wchar
Issue 804: Typos in PIDL to C++ mappings
Issue 863: Read-only restrictions on parameters
Issue 902: CORBA::Bounds and CORBA::TypeCode::Bounds
Issue 914: Mappings for hash, is_equivalent, _is_a and _non_existent
Issue 920: ServantBase mappings
Issue 932: Semantics of >>= operator in C++ mapping CORBA::ORB::InvalidName ambigious in C++ mapping
Issue 933: CORBA::ORB::InvalidName ambigious in C++ mapping
Issue 956: No conversion defined from a B_var to an A_ptr
Issue 1056: Fixed types in orbos/98-01-11
Issue 1069: Typos on p 20-34 of orbos/98-01-11
Issue 1070: macros for fixed arithmetic results
Issue 1072: fixed_digits and fixed_scale member functions
Issue 1073: Missing constructor for Fixed
Issue 1092: C++ mapping for fixed is broken (01)
Issue 1093: C++ mapping for fixed is broken (02)
Issue 1095: Old References in C++ mapping
Issue 1115: TypeCode_ptr base_typecode(TypeCode_ptr tc)
Issue 1124: C++ Fixed type issue (01)
Issue 1125: Fixed type (02)
Issue 1126: C++ Fixed Type (03)
Issue 1128: String member initialization
Issue 1134: C++ Sequence mapping Question
Issue 1137: Typos in parameter passing rules
Issue 1148: Typo in orbos/98-01-11
Issue 1149: _out parameter typo
Issue 1289: How to put a generic CORBA exception into an Any
Issue 1319: C++ Any mapping proposed change
Issue 1383: Missing operators in orbos/98-01-11
Issue 1384: Mapping for wide strings
Issue 1386: Any and WChar issue
Issue 1418: C++ _var type widening proposal
Issue 1519: _var & _out types problems (01) Spec does not mention the existance of an Any_out class
Issue 1520: Spec does not mention the existance of an Any_out class
Issue 1521: Spec is too verse in defining the T_var types for fixed length
Issue 1534: Add _narrow() operation to each POA servant
Issue 1535: Do POA servant classes need to use virtual inheritance?
Issue 1538: Missing text describing fixed point constant mapping
Issue 1617: C++ mapping for strings
Issue 1626: C++ issue to coordinate with proposed resolution of issue 752
Issue 1627: Problems with deactivate_object()
Issue 1631: C++ Servants: Adding Reference counting
Issue 1655: Section 5.3.6.3 Value Factories
Issue 1656: C++ language mapping minor editorial revision
Issue 1657: Section 7.3.5 ValueBase editorial changes
Issue 1658: Parameter passing rules for ValueFactory
Issue 1659: Section 7.3.6: PortableServer::ValueRefCountBase
Issue 1686: resolve_initial_references missing from Orb interface
Issue 1700: void * functions for Any
Issue 1735: Servant management rules
Issue 1747: from_string issue
Issue 1776: New C++ issue about T_out classes
Issue 1777: DSI C++ issue
Issue 1783: Comparison operators for Fixed
Issue 1785: Passing Fixed to operations
Issue 1794: _ptr_type and _var_type typedefs
Issue 1799: struct containing Fixed type
Issue 1898: Fixed-point initialization
Issue 1899: Rounding and truncation of Fixed
Issue 1923: Is SystemException supposed to be concrete?
Issue 1937: Signature of _narrow in exceptions
Issue 1946: sequence allocbuf parameter != 0
Issue 1947: sequence max < length Clarification requested on GIOP 1.1 and wstring
Issue 1971: Extraction of strings from an Any
Issue 1983: Extraction of Fixed from Any
Issue 1984: Generic extraction of Fixed
Issue 2002: The C++ mapping for valuetype _narrow should not _add_ref
Issue 2003: Tie classes
Issue 2029: _primary_interface
Issue 2032: Typedef for ties?
Issue 2035: mapping IDL Unicode escapes to C++
Issue 2097: 98-09-03, exception inconsistency
Issue 2118: Any missing LongLong operators, etc?
Issue 2207: Need more info for custom marshalled value in C++
Issue 2215: Object reference members, _var, and widening
Issue 2222: Is public _ptr member mandatory?
Issue 2226: Errors in example code for boxed struct
Issue 2231: _raise() should be const
Issue 2234: String sequence and allocbuff
Issue 2253: portable includes
Issue 2285: Value Box Mapping
Issue 2286: string allocation functions -- description ambiguous
Issue 2288: C++ spec uses reserved names in global namespace
Issue 2306: Valuetypes as operation arguments
Issue 2309: Memory management of recursive value
Issue 2335: Extraction from Any by pointer
Issue 2345: "Diamond of Death" in CosLifeCycleReference
Issue 2346: Any inserters and extractors
Issue 2350: boxed types for floating point values
Issue 2351: CORBA2.3 C++ mapping for the TypeCode class (section 20.31.2)
Issue 2354: CustomMarshal mapping type
Issue 2355: ORB mapping re Policy
Issue 2357: Misleading text for DSI invoke() and _primary_interface()
Issue 2375: Transfer of C++ codes
Issue 2376: Interface issue
Issue 2441: tie doesn"t do ref counting
Issue 2443: C++ keyword mapping ambiguous
Issue 2445: add a _var type for each servant type
Issue 2453: Any inserters for strings need to use const pointers
Issue 2463: Incorrect types for type-safe Any extraction
Issue 2489: 20.17.9 Valuetype Inheritance
Issue 2496: generate concrete classes and factories for valuetypes without initializer
Issue 2497: Value boxes and sensible value issue
Issue 2498: narrow abstract interface class to concrete object?
Issue 2499: Add AbstractBase base type to IDL language?
Issue 2523: Valuetype argument passing
Issue 2525: string sequences and empty strings
Issue 2530: Sequences and get_buffer()
Issue 2560: Factories for StringValue and WStringValue
Issue 2561: Valuetypes and arbitrary graphs
Issue 2564: Valuetypes and _out classes in C++ mapping
Issue 2614: Setting the TypeCode of an Any without setting a value
Issue 2619: operator>> for String_var CODESET_INCOMPATIBLE exception
Issue 2640: IDL that is not IDL!
Issue 2841: Two obvious typos in the C++ mapping for OBV (docs/formal/99-07-41.pdf)
Issue 2875: ValueBase::_copy_value clarification
Issue 2880: Union string member mapping defect?
Issue 2887: Contents of string members (01)
Issue 2888: Contents of string members (02)
Issue 2890: String extractor semantics undefined?
Issue 2895: Exception::_raise() should be const?
Issue 2897: Exception constructors should be protected
Issue 2902: Unary operators for Fixed class have wrong return types
Issue 2946: CORBA 2.3 Editorial problem in TypeCode
Issue 2947: Object _out class copy constructor & assignment op wrong Editorial typo in Section 1.36.3 of C++ mapping
Issue 2948: Editorial typo in Section 1.36.3 of C++ mapping
Issue 2949: Fixed(const char *) constructor problem
Issue 2950: Fixed::round and truncate issue
Issue 2951: Inconsistency in 1.7 and 1.9 of mapping
Issue 2966: Standard object operations & DynamicImplementation NamedValue not only an NVList element
Issue 2967: NamedValue not only an NVList element
Issue 3055: _default_POA
Issue 3074: Problem with AbstractBase definition
Issue 3078: 1 of 4 issues with Abstract interfaces
Issue 3079: 2 of4 issues with Abstract interfaces
Issue 3080: don't understand the last paragraph of 1.18.2:
Issue 3081: 4 of 4 issues with Abstract interfaces
Issue 3092: Need Any::to_value operation?
Issue 3101: _var types for fixed-length underlying types
Issue 3103: Extraction operator for system exceptions?
Issue 3110: allocbuf() for bounded sequences?
Issue 3111: Abstract interface and DSI issue with C++
Issue 3113: Any::to_abstract_base needs statement about memory management
Issue 3150: Exceptions in servant constructors
Issue 3161: _out types and nested calls
Issue 3165: C++: ostream insertion
Issue 3206: Valuetype code typo in CORBA 2.3 C++ mapping
Issue 3217: Any and UnknownUserException
Issue 3222: C++ valuetype issue (01)
Issue 3223: Valuebox for object reference underspecified
Issue 3224: C++ Value Type issue (02)
Issue 3225: C++ ValueBox & Fixed question PSS: factory_dcl syntax
Issue 3239: Obsolete text in 1.40.3
Issue 3242: C++ spec: Valuebase missing get_value_def
Issue 3245: Construction of _var types
Issue 3246: UnknownUserException and stubs
Issue 3247: fixed-length _var assignment from pointer
Issue 3248: Object Reference insertion/extration to Any
Issue 3298: Problem with OBV_ valuetype class constructor
Issue 3304: Problem with type specific valuetype factories in CORBA 2.3.1 C++ mapping
Issue 3326: ValueBase::_copy_value() function is underspecified
Issue 3328: Do valuetype POA servants get tie templates?
Issue 3331: Valuetype "copying" semantics underspecified? (C++ issue # 1)
Issue 3332: Valuetype "copying" semantics underspecified? (C++ Issue # 2)
Issue 3339: ref counting ambiguous?
Issue 3340: set_servant and null servant
Issue 3359: Issue with valuetypes & inout/out parameters INS Issue: Orderof how the Initial reference is resolved
Issue 3380: Constructor for structures?
Issue 3381: _name and _rep_id
Issue 3401: void * operations on Any?
Issue 3532: DSI and implicit activation
Issue 3534: Null assignment to String_var?
Issue 3537: Sequence mapping & custom marshalling Read-only parameter remnants
Issue 3538: Read-only parameter remnants
Issue 3539: Variable-length out params and exceptions
Issue 3562: Supporting typedefs for _var types?
Issue 3563: Supporting typedefs for _var types?
Issue 3567: Any insertion for Boolean/Octet/Char
Issue 3574: unclear semantics for valuetype insertion into Any
Issue 3603: unspecified criterion for Any extraction
Issue 3604: Any extraction widening to ValueBase
Issue 3616: CORBA::Environment for EH compilers
Issue 3673: CORBA::release and CORBA::is_nil on POA_ptr
Issue 3796: Missing conversion operator on String_var
Issue 3797: Another issue with String_var
Issue 3944: CORBA::Fixed needs a to_string() conversion function
Issue 3966: _default_POA if no default ORB?
Issue 4002: CORBA::RequestSeq or CORBA::ORB::RequestSeq?
Issue 4114: Requiring ref counting in ServantBase
Issue 4119: questions to IDL - C++ mapping ( CORBA 2.3, valuebox)
Issue 4144: ORB::destroy() missing
Issue 4150: Optional parameters for _create_request?
Issue 4151: Passing two context lists to _create_request()
Issue 4153: _name & _rep_id pure virtual? MODL Appendix needs updating
Issue 4157: publication of messaging / unchecked_narrow
Issue 4160: mapping of local interfaces
Issue 4166: Need for TIE template for skeletons for valuetypes that support
Issue 4172: LocalObject
Issue 4186: CORBA::Object & LocalObject class TaggedValuewill two association-ends with the same name "stereotype"
Issue 4199: Inserters/extractors for boxed strings?
Issue 4210: Non-exception neutral code in C++ mapping.
Issue 4243: Backward compatibility with C
Issue 4244: Remnant of read-only return values and out params
Issue 4245: How to create a local object reference?
Issue 4265: Server-side exception specifications and ISO C++ std::exception
Issue 4270: semantics of valuetype _downcast operation unclear
Issue 4274: There is an incorrect page reference
Issue 4288: ServantBase needs _get_domain_managers()?
Issue 4325: Deprecated Ref identifier
Issue 4340: Structure member ordering
Issue 4344: Typedefs for struct members?
Issue 4496: Local interfaces issue 1
Issue 4498: Escaped keyword mapping?
Issue 4499: Dangling reference
Issue 4530: Bug on _var references
Issue 4533: Fixed and truncation/rounding?
Issue 4539: UTF-8 and IDL character types in C++
Issue 4545: C++ mapping for CORBA::LocalObject
Issue 4567: ORB interface destroy() operation issue
Issue 4610: ValueRefCountBase::_add_ref
Issue 4743: Context PIDL mapping bug
Issue 4797: Add set of typedefs that would facilitate template programming
Issue 4871: Missin operations in Object interface, ptc/01-06-07
Issue 5440: Prohibit extracting from any into _out type?
Issue 5450: Typographical problems
Issue 5466: conversion algorithm not specified
Issue 5578: Initialized T_var?
Issue 5579: implementing local interfaces in C++
Issue 5580: No Mapping for Local interface in C++
Issue 5784: need mapping for get_orb and get_component on CORBA::Object
Issue 5807: String_var and C++ implicit conversions
Issue 5854: 1.16.3 Extraction from any
Issue 6163: _var's and valuetypes
Issue 6245: No portable way to create a OUT argument for a DII request
Issue 6276: Sequence _var needs const operator []
Issue 6413: Concrete ValueType _init class problem
Issue 11403: Section: 13.6 Server mapping
Issue 52: Omission in union C++ mapping (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Several problems exist with the definition of union constructors.
Resolution: fixed by adding clarifying text
Revised Text:
Actions taken:
July 11, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 75: Access to sequence buffers (cxx_revision)
Click here for this issue's archive.
Nature: ENHANCEMENT
Severity: Serious
Summary: Summary: We would like to see an enhancement which allows access to sequence buffers once they have been constructed.
Resolution: Fixed
Revised Text:
Actions taken:
August 13, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 91: Efficiency issue in C++ mapping (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: There is a problem with the C++ mapping which requires excessive memory copying in order to be exception safe while constructing a return value.
Resolution: This issue was fixed by Portability Submission
Revised Text:
Actions taken:
August 22, 1996: Received issue
January 2, 1998: closed issue
Discussion:
Issue 92: T__alloc in C mapping (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Is it intended that use of T__alloc functions are the only conformant way to allocate values of (variable length) type T? Or can a conformant app also declare them on the stack?
Resolution: clarified
Revised Text:
Actions taken:
August 27, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 94: Defining an operator for struct/union/sequence _var types (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: If no operator *() is defined for struct, union, or sequence _var types, some pieces of code will break.
Resolution: withdrawn by submitter
Revised Text:
Actions taken:
August 29, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 95: Re-opening modules (cxx_revision)
Click here for this issue's archive.
Nature: Clarification
Severity: Minor
Summary: Summary: Is it legal to split IDL module declarations and to re-open a module similarly to what is done with C++ namespaces?
Resolution: obsolete, cloe issue
Revised Text: Answered in the text of CORBA 2.0.
Actions taken:
August 30, 1996: Received issue
September 1, 1996: Resolved issue
Discussion:
Issue 96: C++ classes for modules (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Does the standard require an implementation to use C++ classes for modules if there is no namespace support? Or is it simply a suggestion?
Resolution: clarified
Revised Text:
Actions taken:
September 3, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 98: In String Argument Passing Question (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: To be compliant, does a client have to pass a string_alloc"ed string to a CORBA operation that takes an in string parameter? If so, why should the ORB care how the client created storage?
Resolution: clarified
Revised Text:
Actions taken:
September 6, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 100: Union discriminators in C++ (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Is a modifier function required under the C++ mapping of unions, and if it is, can it be used to set the discriminator to an illegal value?
Resolution: clarified
Revised Text:
Actions taken:
September 6, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 101: Memory Management Clarification (cxx_revision)
Click here for this issue's archive.
Nature: Clarification
Severity:
Summary: Summary: Should fields of a struct persist across a deep copy?
Resolution:
Revised Text:
Actions taken:
September 6, 1996: Received issue
February 19, 1999: closed issue
Discussion: clarified
Issue 123: Fixed structs (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Should the ORB hide the difference between fixed and variable length structs from the application developer?
Resolution: Close no change. This change is too intrusive and would break too much existing code.
Revised Text:
Actions taken:
September 23, 1996: Received issue
June 13, 2000: closed issue
Discussion:
Issue 125: Passing of object reference in pointers (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Suggest changing the mapping so that object references for an interface "T" are passed as "const T_ptr&" instead of just "T_ptr" for "in" parameters.
Resolution: Close no change. This change is too intrusive and would break too much existing code.
Revised Text:
Actions taken:
September 23, 1996: Received issue
June 13, 2000: closed issue
Discussion:
Issue 134: Union problem (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Is this legal: union X switch(boolean) {case TRUE: short a; case FALSE: long b;default: double c;};? If no, why? If yes, what does _d() return if the union was set with the c() access function?
Resolution: fixed
Revised Text:
Actions taken:
September 24, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 141: Practical problem with DII using Request Pseudo Object (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: If I want to use the DII to send out multiple simultaneous requests, I don"t see a practical way to associate any client specific context that is C++ compliant to those requests.
Resolution:
Revised Text:
Actions taken:
October 1, 1996: Received issue
Discussion:
Issue 142: inserter and extractor functions for exceptions (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: The spec is silent about whether to generate Any inserter and extractor (<<= and >>=) functions for exceptions, although they appear necessary for properly storing and manipulating exceptions.
Resolution: added clarifying texed, fixed
Revised Text:
Actions taken:
October 1, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 143: Testing exceptions (cxx_revision)
Click here for this issue's archive.
Nature: Enhancement
Severity:
Summary: Summary: In the DII, testing what variety of exception is stored in the Request Pseudo-object requires a sequence of dynamic_cast<> or (_narrow) calls. It would be useful to have a single call.
Resolution: closed/resolved
Revised Text: Change the signature of CORBA::Exception on page 1-94 as follows:
// C++
class Exception {
public:
virtual ~Exception();
virtual void _raise() const = 0;
virtual const char * _name() const;
virtual const char * _rep_id() const;
};
Add the following text on page 1-109, preceding the para that introduces UserException:
The _name() function returns the unqualified name of the exception. The _rep_id() function returns the repository
ID of the exception.
Actions taken:
October 1, 1996: Received issue
June 13, 2000: closed issue
Discussion:
Issue 144: Rethrowing exceptions (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: If all I want to do is rethrow an exception in my C++ client code, there is no convenient and compliant way. It would be useful to add extra members to allow this.
Resolution: Fixed by Portability submission
Revised Text:
Actions taken:
October 1, 1996: Received issue
January 2, 1998: closed issue
Discussion:
Issue 145: Missing Any inserter (cxx_revision)
Click here for this issue's archive.
Nature: Clarification
Severity:
Summary: Summary: The following inserter is missing in the C++ spec: void operation <<=(Any &, Any *); // non-copying
Resolution: Fixed in CORBA 2.2 editing process
Revised Text:
Actions taken:
October 1, 1996: Received issue
February 26, 1998: closed issue
Discussion:
Issue 146: Any extractor signature problem (cxx_revision)
Click here for this issue's archive.
Nature: Clarification
Severity:
Summary: Summary: Should the Any extractor signature be (Any_ptr &) instead of (Any &)?
Resolution: Fixed in CORBA 2.2 editing process
Revised Text:
Actions taken:
October 1, 1996: Received issue
February 26, 1998: closed issue
Discussion:
Issue 147: Defintion of Any (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: The definition of Any in C.3 is missing the no_copy flag in the class Any::from_string.
Resolution: Fixed in CORBA 2.2 editing process
Revised Text:
Actions taken:
October 1, 1996: Received issue
February 26, 1998: closed issue
Discussion:
Issue 148: Adding T_copy function (cxx_revision)
Click here for this issue's archive.
Nature: Enhancement
Severity:
Summary: Summary: It would be useful if the C++ mapping for IDL arrays also generated a T_copy() function to go along with T_alloc(), T_dup(), and T_free().
Resolution: Fixed as suggested by submitter
Revised Text:
Actions taken:
October 1, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 150: Any string extractor (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Does the Any string extractor (>>=) return a pointer that is still managed by the Any or a copy? The spec appears to be silent about this.
Resolution: Clarifying text added
Revised Text:
Actions taken:
October 2, 1996: Received issue
February 19, 1999: closed issue
Discussion:
Issue 154: Problem with Any::to_object memory management (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: Section 16.14.5-implies that a CORBA::Object reference extracted from Any must share memory with actual interface stored in Any.Better: results of Any::to_object require explicit release()
Resolution: resolved, close issue
Revised Text:
Actions taken:
October 7, 1996: received issue
February 19, 1999: closed issue
Discussion:
Issue 178: Bounded sequence problem (Section 16.11 p. 16-23) (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary: Summary: "Default constructor for a bounded sequence always allocates a contents vector.."-> Bad effect for sequences such as CORBA::ReferenceDatawhich allocates 1024 octets of storage
Resolution: resolved, close issue
Revised Text:
Actions taken:
October 7, 1996: received issue
February 19, 1999: closed issue
Discussion:
Issue 185: Return value of maximum() for unbounded sequences (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity: CRITICAL
Summary: Summary: Return value of maximum() for unbounded sequences must be specified.
Resolution: resolved, close issue
Revised Text: Paragraph 11 on page 38 fully explains the return values of maximum(), so that it is not an issue. Wording of page 37 para 3 should be similar to wording of first sentence of para 13 p. 38.Wording should be added to front of C++ Mapping Spec that defines
Actions taken:
October 14, 1996: received issue
February 19, 1999: closed issue
Discussion:
Issue 186: Inconsistent interfaces for the operation pairs *duplicate* and (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity: CRITICAL
Summary: Summary: The operations *duplicate* and *release* work together to provide memory mgmt. functionallity. It"s desirable to use both via similar interface/syntax. *nil*/*is_nil* similar problem
Resolution: close with no change
Revised Text:
Actions taken:
October 14, 1996: received issue
June 13, 2000: closed issue
Discussion: Close 186 with no change. Making changes to fundamental parts of the API purely to for stylistic reasons is too high a price to
pay because it would break existing code.
Issue 187: Freeing inaccessible storage for T_var as out parameter (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity: CRITICAL
Summary: Summary: Standard requires that a conforming implementation must free the inaccessable storage associated with a parameter passed as a managed type(T_var). How to achieve it for out parameters??
Resolution: Fixed by Portability submission
Revised Text:
Actions taken:
October 14, 1996: received issue
January 2, 1998: closed issue
Discussion:
Issue 188: interface mapping (cxx_revision)
Click here for this issue's archive.
Nature: Uncategorized
Severity: MEDIUM
Summary: Summary: Mapping for Interface [16.3 CORBA2.0] Mapping example in 3.5.6 implements the ptr type as full pointer. A pointer could be implemented as a class
Resolution: Close no change. This change is too intrusive and would break too much existing code.
Revised Text:
Actions taken:
October 14, 1996: received issue
June 13, 2000: closed issue
Discussion: Proposed resolution: Passing an objref implemented as an object (as opposed to a pointer) as a reference to const requires all the operations supported by that objref to be const member functions.
Issue 189: Distinction between _var and _ptr types (cxx_revision)
Click here for this issue's archive.