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

C Language Mapping RTF — Open Issues

  • Key: C11
  • Issues Count: 55
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
C11-55 OpaqueValue needs to be documented in the C Language mapping C 1.1 open
C11-54 Order of structure members C 1.1 open
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

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

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

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