${taskforce.name} Avatar
  1. OMG Task Force

C Language Mapping RTF — All Issues

  • Key: C11
  • Issues Count: 84
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
C11-82 How to allocate storage for a basic type you wish to place in an any? C 1.0b1 C 1.1 Resolved closed
C11-81 Use of "objref_ptr" C 1.0b1 C 1.1 Resolved closed
C11-83 Correct arguments to send multiple requests C 1.0b1 C 1.1 Resolved closed
C11-73 Out of bound value behaviour for _maximum and _length in sequences C 1.0b1 C 1.1 Resolved closed
C11-72 Type declaration C 1.0b1 C 1.1 Resolved closed
C11-76 Order of parameters in the C mapping C 1.0b1 C 1.1 Resolved closed
C11-75 Editorial C 1.0b1 C 1.1 Resolved closed
C11-80 CORBA_string_alloc C 1.0b1 C 1.1 Resolved closed
C11-79 Argument order inconsistent (Section 14.25.2) C 1.0b1 C 1.1 Resolved closed
C11-74 Portably getting the value of the bounds of a sequence C 1.0b1 C 1.1 Resolved closed
C11-78 Reference to undefined term DIR (Section 14.24.1) C 1.0b1 C 1.1 Resolved closed
C11-71 Order of arguments in C Language mapped operation C 1.0b1 C 1.1 Resolved closed
C11-77 Wrong order of parameters C 1.0b1 C 1.1 Resolved closed
C11-64 Semantics of CORBA_exception_id()"s return type C 1.0b1 C 1.1 Resolved closed
C11-63 Suggested optimization for string duplication C 1.0b1 C 1.1 Resolved closed
C11-59 Unions represented with either union or struct C 1.0b1 C 1.1 Resolved closed
C11-58 All interfaces must be defined at global scope? C 1.0b1 C 1.1 Resolved closed
C11-70 Confusion about ORB handling call to pseudo objects via DII C 1.0b1 C 1.1 Resolved closed
C11-69 Entire section 14.1 should not be there (CORBA 14) C 1.0b1 C 1.1 Resolved closed
C11-67 CORBA_BOA_set_exception() parameter issues C 1.0b1 C 1.1 Resolved closed
C11-66 Specification type on CORBA_ORB_object_to_string example C 1.0b1 C 1.1 Resolved closed
C11-60 Sequence release flag implementation C 1.0b1 C 1.1 Resolved closed
C11-68 Support for efficient DII invocation (Section 17.7.1 CORBA 2.)) C 1.0b1 C 1.1 Resolved closed
C11-65 Contents of string literal exception identifier C 1.0b1 C 1.1 Resolved closed
C11-62 Malloc problems with sequence types C 1.0b1 C 1.1 Resolved closed
C11-61 Confusing sequence example C 1.0b1 C 1.1 Resolved closed
C11-56 C keywords C 1.0b1 C 1.1 Resolved closed
C11-55 OpaqueValue needs to be documented in the C Language mapping C 1.1 open
C11-57 Problems with underscores C 1.0b1 C 1.1 Resolved closed
C11-54 Order of structure members C 1.1 open
C11-84 Content of an Any is a pointer to the type -- Issue C 1.0b1 C 1.1 Resolved closed
C11-44 Bound seq buffer allocation C 1.0b1 open
C11-43 Seq buffer deallocation C 1.0b1 open
C11-42 Mapping for Aliases C 1.0b1 open
C11-41 Exception id name C 1.0b1 open
C11-38 Sequence buffer release C 1.0b1 open
C11-37 Sequence buffer initialization C 1.0b1 open
C11-34 Allocation and initialization C 1.0b1 open
C11-33 Exception initialization C 1.0b1 open
C11-40 Argument passing, cases 3 and 6 C 1.0b1 open
C11-39 Exception initialization and release C 1.0b1 open
C11-36 Sequence initialization C 1.0b1 open
C11-35 De-allocation and release C 1.0b1 open
C11-32 System Exception Type C 1.0b1 open
C11-7 implementation hints not specification (Section 14.24.2 last para) C 1.0b1 open
C11-6 Parameter memory freeing problem (Section 14.24.1.para 6) C 1.0b1 open
C11-11 C mapping for sequence (Section 14.11 CORBA 2.0) C 1.0b1 open
C11-10 inconsistent parameter name and order C 1.0b1 open
C11-15 vec10 and CORBA_sequence_long C 1.0b1 open
C11-14 Spec contains mutually inconsistent examples C 1.0b1 open
C11-18 sequence as anonymous type in struct C 1.0b1 open
C11-17 Declare and define Allocators for new sequence type C 1.0b1 open
C11-8 What happens when set_exception called more than once? C 1.0b1 open
C11-13 C mapping for Any C 1.0b1 open
C11-12 Representation of "string" values in an "any" C 1.0b1 open
C11-16 Allocation Functions for sequences of "T" C 1.0b1 open
C11-9 confusing presentation (Section 14.25.4) C 1.0b1 open
C11-53 Error in C language specification C 1.0b1 open
C11-52 Inconsistency in CORBA 2.0 C mapping C 1.0b1 open
C11-47 Example inconsistent with table 20 and table 21 C 1.0b1 open
C11-46 Seq buffer allocation C 1.0b1 open
C11-51 CORBA_string is not defined C 1.0b1 open
C11-50 No defined value for CORBA_OBJECT_NIL C 1.0b1 open
C11-49 Delete 14.17 para 1 C 1.0b1 open
C11-48 Initial state of out parameter pointers C 1.0b1 open
C11-45 release flag & returned data C 1.0b1 open
C11-4 Pseudo-Object underspecification C 1.0b1 open
C11-3 C Language header question C 1.0b1 open
C11-5 Inappropriate information (Sect. 14.23. last paragraph C 1.0b1 open
C11-1 Inout sequence/any behavior with oversized return values C 1.0b1 open
C11-2 Wrong placement of asterics in table C 1.0b1 open
C11-21 memory allocation functions C 1.0b1 open
C11-20 When MUST _buffer of sequence be allocated with _allocbuf C 1.0b1 open
C11-28 Exception release function C 1.0b1 open
C11-27 Exception stringification C 1.0b1 open
C11-25 Sequence buffer management C 1.0b1 open
C11-24 Sequence behavior C 1.0b1 open
C11-31 Minor field of system exceptions C 1.0b1 open
C11-30 Exception identification C 1.0b1 open
C11-26 Scoped sequence naming C 1.0b1 open
C11-22 memory release functions C 1.0b1 open
C11-23 mapping for sequences C 1.0b1 open
C11-29 CORBA_Environment initialization C 1.0b1 open
C11-19 CORBA_sequence_long C 1.0b1 open

Issues Descriptions

How to allocate storage for a basic type you wish to place in an any?

  • Key: C11-82
  • Legacy Issue Number: 2533
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Under the C mapping how do you allocate storage for a basic type
    you wish to place in an any.

    Consider inserting a long into an Any.

    Do you do this: solution 1

    any->_type = TC_long;
    any->_value = CORBA_alloc(sizeof(CORBA_long));

    or this: solution 2

    any->_type = TC_long;
    any->value = CORBA_long_alloc();

    One vendor argues that the text below supports solution 2. However
    as a long is not a constructed type solution 1 seems more natural.

    >From "17.8 Mapping Considerations for Constructed Types" of CORBA 2.1
    specification:

    "For types whose parameter passing modes require heap allocation,
    an ORB implementation will provide allocation functions. These types
    include variable-length struct, variable-length union, sequence, any,
    string, wstring and array of a variable-length type. The return value
    of these allocation functions must be freed using CORBA_free(). For
    one of these listed types T, the ORB implementation will provide
    the following type-specific allocation function:

    T *T__alloc(); /* C */"

  • Reported: C 1.0b1 — Fri, 12 Mar 1999 05:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    urgent resolution, issue resolved

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Use of "objref_ptr"

  • Key: C11-81
  • Legacy Issue Number: 332
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Nothing defines what an "objref_ptr" is. This was presumably pasted in from C++ mapping which has a T_ptr concept. Stop using this term in the C mapping or define it

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed in CORBA 2.2 editing process

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Correct arguments to send multiple requests

  • Key: C11-83
  • Legacy Issue Number: 2534
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Additional Commentary:

    In tset/c/hdr/DII/ORB/send_multiple_requests.c,
    VSOrb 1.1.0 test examines our orb on the assumption that
    send_multiple_requests() is defined like the following.

    CORBA_Status CORBA_send_multiple_requests(
    CORBA_ORB orb,
    CORBA_Request reqs[],
    CORBA_long count,
    CORBA_Flags invoke_flags,
    CORBA_Environment *env
    );

    But, according to section 4.3.2 of CORBA 2.1 specification,
    send_multiple_requests() is defined like the following.

    /* C */
    CORBA_Status CORBA_send_multiple_requests(
    CORBA_Request reqs[],
    CORBA_Environment *env,
    CORBA_long count,
    CORBA_Flags invoke_flags
    );

    Section C - Interpretation Responses

    The Open Group Initial Response:
    An interpretation from OMG is required to determine whether Section
    4.3.2 or Section 17.17 of CORBA 2.1 is definitive.

    Consultants Initial Response:
    We believe Section 4.3.2 is incorrect according to the general
    C mapping rules (as are many of the other examples). We are
    following rules defined in Section 17.17 which states that every
    function signature takes the object as the first parameter and an
    Environment object as the last parameter.

    Interpretations Subgroup Responses:

  • Reported: C 1.0b1 — Fri, 12 Mar 1999 05:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    urgent resolution....issue closed

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Out of bound value behaviour for _maximum and _length in sequences

  • Key: C11-73
  • Legacy Issue Number: 161
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.11. Para 6 indicates error to set _length or _maximum member larger than specified bound. Say "If the _length and _maximum members are set to a value larger than specified...."

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    replace sentence

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Type declaration

  • Key: C11-72
  • Legacy Issue Number: 160
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.5. ISO C permits declaration of anonymous structures when type is being defined. From a coding style perspective it"s better to require use of defined type names

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    close

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Order of parameters in the C mapping

  • Key: C11-76
  • Legacy Issue Number: 164
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.15: Bullet 2 indicates that last parameter to each operation is an output parameter..Inconsistent with lead sentence, CORBA 1.2, and not reflectedin rest of doc.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed by Portability submission

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Editorial

  • Key: C11-75
  • Legacy Issue Number: 163
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.13: Para 6 Change "For an array T..." to "An array T..."

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed in CORBA 2.2 editing process

  • Updated: Fri, 6 Mar 2015 20:57 GMT

CORBA_string_alloc

  • Key: C11-80
  • Legacy Issue Number: 330
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Editorial issue: The definition on page 14-15 is given as char* CORBA_string_alloc(CORBA_unsigned_long_len); The return type should be "CORBA_char*".

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed in CORBA 2.2 editing process

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Argument order inconsistent (Section 14.25.2)

  • Key: C11-79
  • Legacy Issue Number: 173
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: C signature for example4_op5 as well as CORBA_BOA_set_exception have the environment parameter in the wrong place

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed by Portability Submission

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Portably getting the value of the bounds of a sequence

  • Key: C11-74
  • Legacy Issue Number: 162
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.11: It"s not clear how a portable application could know value of bound of sequence. It"s specified in PIDL but is not represented in generated C header

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    add sentence

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Reference to undefined term DIR (Section 14.24.1)

  • Key: C11-78
  • Legacy Issue Number: 170
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Paragraph refers to "DIR". This term has not been recently defined in the specification.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed in CORBA 2.2 editing process

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Order of arguments in C Language mapped operation

  • Key: C11-71
  • Legacy Issue Number: 159
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Order of arguments to C Language mapped operations seems to have changed from CORBA 1.2. Order must remain the same. Order must be used consistently throughout this specification .

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed by Portability submission

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong order of parameters

  • Key: C11-77
  • Legacy Issue Number: 168
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Example CORBA_ORB_object_to_string function shows CORBA 1.2 function argument ordering. This is inconsistent with text in sect. 14.15. Spec must be internally consistent.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed by Portability submission

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Semantics of CORBA_exception_id()"s return type

  • Key: C11-64
  • Legacy Issue Number: 112
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: CORBA_exception_id() returns a pointer to the character string indentifying the exception. It would be nice to explicitly say that this is the same string defined in 14.14.

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Replace sentence to clarify

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Suggested optimization for string duplication

  • Key: C11-63
  • Legacy Issue Number: 110
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It would be useful if CORBA_string_alloc() took an "optional" second argument which would be the string value to initialize the new string to, since ANSI C does not have strdup().

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Close with no change

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Unions represented with either union or struct

  • Key: C11-59
  • Legacy Issue Number: 106
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In section 14-10 of the C mapping, it says that an ORB can use a struct to hold a union. Doesn"t this cause portability problems?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Close with no change

  • Updated: Fri, 6 Mar 2015 20:57 GMT

All interfaces must be defined at global scope?

  • Key: C11-58
  • Legacy Issue Number: 105
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.3 of the C mapping says that interface definitions may not occur within the scope of module declarations. Doesn"t it mean "within the scope of another interface definition"?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Confusion about ORB handling call to pseudo objects via DII

  • Key: C11-70
  • Legacy Issue Number: 158
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Par. 14.1.8 indicates that ORB may handle calls to pseudo-objects via DII specially. This spec. should indicate that DII can"t be portably used for pseudo-object references.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    close – paragraph is deleted

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Entire section 14.1 should not be there (CORBA 14)

  • Key: C11-69
  • Legacy Issue Number: 157
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Entire section should not be here.It"s relevant to all potential language mappings. It should be moved to an appendix, since it is not a normative part of the specification

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    delete section

  • Updated: Fri, 6 Mar 2015 20:57 GMT

CORBA_BOA_set_exception() parameter issues

  • Key: C11-67
  • Legacy Issue Number: 115
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Who owns the parameters "exceptname" and "param" to CORBA_BOA_set_exception? Shouldn"t that routine take a second CORBA_Environment parameter to signal errors in its operation?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    POA update eliminated conditions - close

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Specification type on CORBA_ORB_object_to_string example

  • Key: C11-66
  • Legacy Issue Number: 114
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: On p. 14-24, the example of CORBA_ORB_object_to_string seems to have the CORBA_environment parameter in an unexpected position. Is this intentional? And what about the example on 14-28?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Fixed by Portability submission

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Sequence release flag implementation

  • Key: C11-60
  • Legacy Issue Number: 107
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.11 of the C mapping introduces a release flag hidden inside the C struct; however, that struct is completely specified and leaves no bit for that flag. How does this work?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Close with no change

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Support for efficient DII invocation (Section 17.7.1 CORBA 2.))

  • Key: C11-68
  • Legacy Issue Number: 155
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Sun wants to ensure that DII interface permits implementations that support invocations without consulting the interface repository as intended by CORBA.

  • Reported: C 1.0b1 — Mon, 7 Oct 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    close

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Contents of string literal exception identifier

  • Key: C11-65
  • Legacy Issue Number: 113
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.14 calls for a string literal which "uniquely identifies this exception type", but does not specify any rules for generating such identifiers.

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Close with no change

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Malloc problems with sequence types

  • Key: C11-62
  • Legacy Issue Number: 109
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The C mapping allocation procedures (T__alloc()) don"t allow for malloc"ing space for both the header struct and the values in one call.

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Close with no change

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Confusing sequence example

  • Key: C11-61
  • Legacy Issue Number: 108
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The fact that a sequence of longs is to be mapped into a struct is very confusing.

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    Close with no change

  • Updated: Fri, 6 Mar 2015 20:57 GMT

C keywords

  • Key: C11-56
  • Legacy Issue Number: 53
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There seems to be no provision for the possibility of C keywords appearing in IDL.

  • Reported: C 1.0b1 — Thu, 11 Jul 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    resolved and closed

  • Updated: Fri, 6 Mar 2015 20:57 GMT

OpaqueValue needs to be documented in the C Language mapping

  • Key: C11-55
  • Legacy Issue Number: 5778
  • Status: open  
  • Source: Thematix Partners LLC ( Jishnu Mukerji [X] (Inactive))
  • Summary:

    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.

  • Reported: C 1.1 — Wed, 27 Nov 2002 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Problems with underscores

  • Key: C11-57
  • Legacy Issue Number: 104
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The C mapping advises avoiding the indiscriminate use of underscores in identifiers. To whom is this addressed? Should it be a more general restriction?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    resolved

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Order of structure members

  • Key: C11-54
  • Legacy Issue Number: 4341
  • Status: open  
  • Source: Triodia Technologies Pty Ltd ( Michi Henning)
  • Summary:

    The C mapping says in section 1.9:

    OMG IDL structures map directly onto C structs. Note that all OMG
    IDL types that map to C structs may potentially include padding.

    This is not as clear as it should be. In particular, a requirement should
    be added to preserve the order of structure members as they appear in the
    IDL.

  • Reported: C 1.1 — Tue, 12 Jun 2001 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Content of an Any is a pointer to the type -- Issue

  • Key: C11-84
  • Legacy Issue Number: 2563
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In PIN4O.00001 OMG have ruled that the content of an any is a
    pointer to the type. So a long in an Any looks like this;

    any ----> long

    But what about strings? As this type includes a pointer part
    itself the above rules would make the following appear to be the
    conformant case;

    any----> ptr to string -----> string : option 1

    Having a pointer to a pointer is a bit unwieldy but appears to follow
    the rules. Collapsing this to simply a pointer to the str thus;

    any----> string : option 2

    is more natural for programmers but ambiguous within the spec.

    We would like to know which of these two options is correct.

    Section C - Interpretation Responses

    The Open Group Initial Response:
    This request is being sent for review by OMG. We request that OMG
    rule which of the two options is correct or whether both are equally
    so.

    Consultants Initial Response:
    We recommend this request be sent to OMG for a binding interpretation.

    We recommend a PIN be granted to clarify the requirements for branding
    irrespective of which of the two options OMG selects.

  • Reported: C 1.0b1 — Tue, 30 Mar 1999 05:00 GMT
  • Disposition: Resolved — C 1.1
  • Disposition Summary:

    urgent resolution, issue closed

  • Updated: Fri, 6 Mar 2015 20:57 GMT

Bound seq buffer allocation

  • Key: C11-44
  • Legacy Issue Number: 334
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: What if user calls T_allocbuf for a bound sequence with a length that doesn"t match sequence constraint?Does this go undetected?. A related issue is issue # 108

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Seq buffer deallocation

  • Key: C11-43
  • Legacy Issue Number: 333
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Sequence buffers are allocated seperately from sequence which contain them, they can be released separately as well. Is this the job of the omnipotent CORBA_free?

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Mapping for Aliases

  • Key: C11-42
  • Legacy Issue Number: 331
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Mapping for IDL typedefs was dropped between CORBA 1.2 and 2.0. It should explicitly stated. Restoring text from 1.2 mapping is probably sufficient

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Exception id name

  • Key: C11-41
  • Legacy Issue Number: 329
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Loose specification of the #define generated for an exception id: Specification by example is never a good idea. The specification should be more explizit.

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Sequence buffer release

  • Key: C11-38
  • Legacy Issue Number: 326
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate a Seq_releasebuf function for sequence Seq of type T to perform any buffer internal release. Function is called by Seq_freebuf prior to free buffer pointer acc. to release flag

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Sequence buffer initialization

  • Key: C11-37
  • Legacy Issue Number: 325
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate a Seq_initbuf function to initialize a buffer for sequence Seq of type T. Seq__allocbuf allocates a buffer and calls seq_initbuf to initialize the allocated buffer

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Allocation and initialization

  • Key: C11-34
  • Legacy Issue Number: 322
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate pairs of (T_init, T_alloc) functions for any type T (with descriptions described in issue # 309 concerning T_alloc)

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Exception initialization

  • Key: C11-33
  • Legacy Issue Number: 321
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Define 2 functions, CORBA_exception_init and CORBA_systemException_init to initialize respectively user-defined exceptions and system exceptions to be raised

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Argument passing, cases 3 and 6

  • Key: C11-40
  • Legacy Issue Number: 328
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Table 22,p 14-20 of C mapping lists argument passing cases. In both cases(3+6) the value is either an out parameter or return value. How to handle CORBA_free as caller or callee

  • Reported: C 1.0b1 — Thu, 7 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Exception initialization and release

  • Key: C11-39
  • Legacy Issue Number: 327
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: generate pairs of (E_init, E_alloc) and (E_release, E_free) functions for exception E with behavior similar to the corresponding functions defined for any type T.

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Sequence initialization

  • Key: C11-36
  • Legacy Issue Number: 324
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: State as undefined the behavior of a sequence as long as its Seq_init function (as specified in issue # 322) has not been called this function initializing the release flag.

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

De-allocation and release

  • Key: C11-35
  • Legacy Issue Number: 323
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate pairs of (T_release, T_free) functions for any type T T_release performs any internal memory release T_free calls T_release and frees the pointer argument

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

System Exception Type

  • Key: C11-32
  • Legacy Issue Number: 320
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Define the type of system exceptions to be typedef definitions of a generic system exception type CORBA_SystemException

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

implementation hints not specification (Section 14.24.2 last para)

  • Key: C11-7
  • Legacy Issue Number: 172
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Para describes strategy an implementation will use for determining an exception TypeCode. Information not relevant to application developer. Mark as guidance to Implementor.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Parameter memory freeing problem (Section 14.24.1.para 6)

  • Key: C11-6
  • Legacy Issue Number: 171
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Para indicates that all the parameter memory is freed as appropriate when DIR returns. Who frees memory? If DIR frees memory, then change the wording as appropriate.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

C mapping for sequence (Section 14.11 CORBA 2.0)

  • Key: C11-11
  • Legacy Issue Number: 177
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Section D.11 presents C mapping for sequence. For performance reasons, Sun prefers to embed the release flag in the sequence.

  • Reported: C 1.0b1 — Mon, 7 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

inconsistent parameter name and order

  • Key: C11-10
  • Legacy Issue Number: 176
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: In the definition of CORBA_ORB_init environment parameter comes last and it uses env instead of ev. Same inconsitency in CORBA_ORB_list_initial_services/CORBA_ORB_list_initial_references

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

vec10 and CORBA_sequence_long

  • Key: C11-15
  • Legacy Issue Number: 292
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: vec10 and CORBA_sequence_long: are these distinct types?Would they have distinct typecodes and distinct entries in the Interface Repository?

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Spec contains mutually inconsistent examples

  • Key: C11-14
  • Legacy Issue Number: 291
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Spec contains mutually inconsistent example (p 14-11 and 14-13. P 14-13 suggests that C structure MUST be named CORBA_sequence_long instead and must be enclosed in #ifdef...#endif

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

sequence as anonymous type in struct

  • Key: C11-18
  • Legacy Issue Number: 295
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: When sequence occurs as anonymous (local) type in a struct,union,etc, how should this be treated?

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Declare and define Allocators for new sequence type

  • Key: C11-17
  • Legacy Issue Number: 294
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Are we supposed to declare and define allocators for new sequence Type? What is acceptable, required, forbidden (in terms of functions)?

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

What happens when set_exception called more than once?

  • Key: C11-8
  • Legacy Issue Number: 174
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Sec 14.25.2: It"s not clear what happens if CORBA_BOA_set_exception is called more than once for a given object invocation. This should be specified.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

C mapping for Any

  • Key: C11-13
  • Legacy Issue Number: 243
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Section D.7 describes the mapping for CORBA_any. Sun would like to replace current C mapping for Any with opaque type, i.e conforming applications may not access members of CORBA_any struct

  • Reported: C 1.0b1 — Mon, 14 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Representation of "string" values in an "any"

  • Key: C11-12
  • Legacy Issue Number: 181
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: In C mapping what is representation of "string" in _value field of an any? "char *" or "char **"? "char **" seems to be more applicable-usage requires an "_alloc" function

  • Reported: C 1.0b1 — Mon, 7 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Allocation Functions for sequences of "T"

  • Key: C11-16
  • Legacy Issue Number: 293
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The spec mentions 2 allocation functionsfor sequences of "T". These should better be inside the same (or similar) #ifdef...#endif as the struct typedef

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

confusing presentation (Section 14.25.4)

  • Key: C11-9
  • Legacy Issue Number: 175
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: It refers to a "third case", but there are no cases described, and there are only 2 examples. What are the cases this paragraph refers to?

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Error in C language specification

  • Key: C11-53
  • Legacy Issue Number: 2307
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: There is very probably a small error in the C language specification.
    Below is what I wrote to the mailing list concerned with building the ORBit ORB. It
    was confirmed by one of the main coders behind ORBit.

    > This is something else, but I was more confused because the OMG "C language
    > mapping" spec at page 19-39 really seems to contain an error.
    > In that example, they also create an application specific servant structure called
    > AppServant, and they set the finalizer using
    >
    > AppServant my_servant = ...
    >
    > my_servant.epv._base_epv.finalize = my_finalizer_func;
    >
    > That should really have been (at least, that"s what I think):
    >
    > my_servant.base.vepv._base_epv.finalize = my_finalizer_func;
    >
    > I hope you agree with me there, or else I"m probably getting out of touch with C.

  • Reported: C 1.0b1 — Mon, 18 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Inconsistency in CORBA 2.0 C mapping

  • Key: C11-52
  • Legacy Issue Number: 636
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: I currently implement a subset of CORBA 2.0. Not CORBA-compliant in terms of C-mapping for arguments to pseudo-objects and real objects. Give clear statement on argument order for real objects

  • Reported: C 1.0b1 — Tue, 29 Jul 1997 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Example inconsistent with table 20 and table 21

  • Key: C11-47
  • Legacy Issue Number: 462
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Example foo::bar on page 14-17 has fixed array out parameter. Mapping shown on this page doesn"t agree with tables 20 and 21.

  • Reported: C 1.0b1 — Wed, 11 Dec 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Seq buffer allocation

  • Key: C11-46
  • Legacy Issue Number: 336
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Sec 14.11 specifies generation of a buffer allocator for each sequence type of form T* sequence_T_allocbuf (CORBA_unsigned_long_len); very difficult to implement correctly.

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CORBA_string is not defined

  • Key: C11-51
  • Legacy Issue Number: 620
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.28.1, 14.28.2, 14.29: CORBA_string is not defined anywhere in the code sample. These should be typedefed as CORBA_char * or char *

  • Reported: C 1.0b1 — Wed, 9 Jul 1997 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

No defined value for CORBA_OBJECT_NIL

  • Key: C11-50
  • Legacy Issue Number: 606
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.3: Reference is made to CORBA_OBJECT_NIL but there is no defined value for this. A value must be explicitly defined and typed

  • Reported: C 1.0b1 — Wed, 9 Jul 1997 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Delete 14.17 para 1

  • Key: C11-49
  • Legacy Issue Number: 486
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The first para of section 14.17 seems to have crept back after a deletion in a n earlier draft- it shouldn"t since it generalizes things (wrongly) which are properly described later

  • Reported: C 1.0b1 — Tue, 14 Jan 1997 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Initial state of out parameter pointers

  • Key: C11-48
  • Legacy Issue Number: 485
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Spec. should be clear that the pointer passed in out parameters by caller should be uninitialized. This clarification should be in case (3) and (6) of Table 22

  • Reported: C 1.0b1 — Tue, 14 Jan 1997 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

release flag & returned data

  • Key: C11-45
  • Legacy Issue Number: 335
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Mapping should be explicit about how release flag interacts with inout, out, and return parameter. There probably is arelated C++ issue

  • Reported: C 1.0b1 — Thu, 31 Oct 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Pseudo-Object underspecification

  • Key: C11-4
  • Legacy Issue Number: 167
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Sect.14.23: Section indicates that ORBs may restrict the scope of legal operations on pseudo-objects. Minimal subset of operations should be defined so port. applications know what to rely on.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

C Language header question

  • Key: C11-3
  • Legacy Issue Number: 166
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.22: Al IDL compilers will generate a C language header. Does that mean that the C Language is required to be supported by all CORBA implementations?

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Inappropriate information (Sect. 14.23. last paragraph

  • Key: C11-5
  • Legacy Issue Number: 169
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Information on implementation strategies for pseudo-objects is not relevant to application portability. It should be removed or appropriately annotated as guidance for ORB implementors.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Inout sequence/any behavior with oversized return values

  • Key: C11-1
  • Legacy Issue Number: 111
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: In case 5 of table 22 in section 14.19, what is the specified behavior if the release flag is FALSE, but the value to be returned is longer than the value specified?

  • Reported: C 1.0b1 — Wed, 11 Sep 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Wrong placement of asterics in table

  • Key: C11-2
  • Legacy Issue Number: 165
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Section 14.19: Asteriks in table are meant to indicate that item is a C Language pointer. They should not be subscribed.

  • Reported: C 1.0b1 — Thu, 10 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

memory allocation functions

  • Key: C11-21
  • Legacy Issue Number: 309
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate T__alloc functions for any type T except interfaces: no function, any: CORBA_any_alloc string: CORBA_string_alloc

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

When MUST _buffer of sequence be allocated with _allocbuf

  • Key: C11-20
  • Legacy Issue Number: 297
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: When must this be done? always, whenever the release flag is TRUE, whenever the sequence elements contain secondary storage, whenever it is an out, inout, or return

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Exception release function

  • Key: C11-28
  • Legacy Issue Number: 316
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate a E_free function dual to Ealloc for exception E. /* C API / void E_free (E);

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Exception stringification

  • Key: C11-27
  • Legacy Issue Number: 315
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate string literal for exceptions as the stringification of the macro name e.g.for exception E: /*C code generation */ #define ex_E "ex_E"

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Sequence buffer management

  • Key: C11-25
  • Legacy Issue Number: 313
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Generate a pair of (Seq_allocbuf, Seq_freebuf) functions, for sequence Seq of type T to manage resource of buffer sequences: Seqallocbuf and Seq_freebuf

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Sequence behavior

  • Key: C11-24
  • Legacy Issue Number: 312
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The proposal is to state as undefined the behavior of a sequence as lon as its release flag has not been initialized

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Minor field of system exceptions

  • Key: C11-31
  • Legacy Issue Number: 319
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Define the _minor field of system exceptions to be of type CORBA_ExceptionMinor

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Exception identification

  • Key: C11-30
  • Legacy Issue Number: 318
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Reserve the CORBA_exception_id function for user-defined exceptions only.

  • Reported: C 1.0b1 — Thu, 1 Jul 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Scoped sequence naming

  • Key: C11-26
  • Legacy Issue Number: 314
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Map sequence type names and sequence element type names enclosed within a scope according to the encoding scheme described as follows (/archives/issues/issue314)

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

memory release functions

  • Key: C11-22
  • Legacy Issue Number: 310
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Deprecate use of CORBA_free and generate T_free functions for any type T instead. Specification of T_free is current spec for CORBA_free suitable for type T

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

mapping for sequences

  • Key: C11-23
  • Legacy Issue Number: 311
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Add release flag to generated C structure and map IDL sequence type from following definition (/archives/issues/issue311)

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CORBA_Environment initialization

  • Key: C11-29
  • Legacy Issue Number: 317
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Define a library function CORBA_Environment_init to initialize the non-opaque fields of CORBA_Environment (see file)

  • Reported: C 1.0b1 — Mon, 25 Nov 1996 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

CORBA_sequence_long

  • Key: C11-19
  • Legacy Issue Number: 296
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Why is it not CORBA_sequence_CORBA_long? What is the precise rule by which these names are constructed?

  • Reported: C 1.0b1 — Tue, 22 Oct 1996 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT